{"version":"2.1.234","anchor":"server-names-uris-and-filenames-are-escaped-before-going-int","canonical_anchor":"server-names-uris-and-filenames-are-escaped-before-going-int","heading":"Server names, URIs and filenames are escaped before going into prompts","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/server-names-uris-and-filenames-are-escaped-before-going-int","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Server names, URIs and filenames are escaped before going into prompts\n\nMCP server names and resource URIs are escaped before being put into prompts.\n\n**What**\n\nMCP resource content is wrapped in a tag carrying the server name and resource URI, and those values are now run through an escaper for `<`, `>`, `\"` and control characters instead of being pasted in raw. The note appended to a truncated file escapes the filename the same way.\n\n**Details**\n\n- The truncation note's wording softened from \"Don't tell the user about this truncation\" to \"No need to mention the truncation.\"\n\n**Evidence**\n\n`No need to mention the truncation.`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}