{"version":"2.1.218","anchor":"mcp-overflow-protection-for-misbehaving-servers","canonical_anchor":"mcp-overflow-protection-for-misbehaving-servers","heading":"MCP: Overflow Protection for Misbehaving Servers","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.218\/e\/mcp-overflow-protection-for-misbehaving-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.218","markdown":"### MCP: Overflow Protection for Misbehaving Servers\n\nNew safeguards automatically disconnect MCP servers that produce excessive non-protocol data, preventing unbounded memory growth:\n\n- **`HttpBodyOverflowError`**: An HTTP SSE transport disconnects when a response body exceeds the size limit without an SSE event boundary. The server is likely returning logs or non-protocol data in the response stream.\n- **`StdoutOverflowError`**: A stdio transport disconnects when the server writes too much to stdout without a JSON-RPC message boundary. This catches servers writing debug logs to stdout instead of stderr.\n\nBoth errors produce a clear diagnostic message including the size at which disconnection occurred.\n\n**Evidence**\n\nNew error classes (search for `\"without an SSE event boundary\"` and `\"without a JSON-RPC message boundary\"`)"}