{"version":"2.1.248","anchor":"mcp-server-and-tool-names-are-escaped-in-control-loop-error-","canonical_anchor":"mcp-server-and-tool-names-are-escaped-in-control-loop-error-","heading":"MCP server and tool names are escaped in control-loop error replies","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-server-and-tool-names-are-escaped-in-control-loop-error-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP server and tool names are escaped in control-loop error replies\n\nServer and tool names quoted in error replies are now escaped first.\n\n**What**\n\nError responses that quote a server or tool name back to the caller now pass that name through a sanitizing helper instead of dropping it in raw, so an odd name cannot alter the message around it.\n\n**Details**\n\n- Covers `Server not found:`, the enterprise managed-policy block message, `Not a fully-qualified MCP tool name:`, `mcp_call cancelled by client:` and `MCP server not connected:`.\n- Applies on every one of those paths with no condition. What exactly the helper strips is not visible from this code.\n\n**Evidence**\n\n`MCP server not connected: `\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}