iter

The Iter Server places a very strong emphasis on security at its MCP boundary. It implements extensive input validation for all parameters (belief, energy, weight, node IDs, payload sizes) and enforces a hardened, deterministic response sanitization layer. This sanitizer actively strips forbidden patterns, applies Unicode normalization, and removes zero-width characters to prevent leakage of internal engine details such as DAG topology, raw ESV values, energy matrices, stack traces, or other debug information. The architecture explicitly prohibits public export of internal substrate types, ensuring all external interactions are via sanitized DTOs. While a `CallerContext` placeholder exists for future authentication/authorization, the core sanitization is always active. The server primarily uses STDIO for transport, which can limit direct network exposure if run as a subprocess within a secure wrapper.