{"version":"2.1.234","anchor":"mcp-resource-results-escape-server-names-and-uris","canonical_anchor":"mcp-resource-results-escape-server-names-and-uris","heading":"MCP resource results escape server names and URIs","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/mcp-resource-results-escape-server-names-and-uris","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### MCP resource results escape server names and URIs\n\nMCP resource results escape hostile server names and URIs so they can't break out of the wrapper.\n\n**What**\n\nThe wrapper Claude Code builds around a resource fetched from an MCP server now escapes the server name and resource URI before putting them in the text, so a hostile name or URI cannot break out of the wrapper. The empty result case now comes from the same shared builder rather than a separate inline string.\n\n**Evidence**\n\n`(No content)`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}