{"version":"2.1.295","anchor":"mcp-error-text-redaction-hardened","canonical_anchor":"mcp-error-text-redaction-hardened","heading":"Hiding configuration details in MCP error messages is now harder to overload","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-error-text-redaction-hardened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Hiding configuration details in MCP error messages is now harder to overload\n\nMCP error redaction now limits its total work and stops with a message when the error repeats too much of the configuration\n\n**What**\n\nMCP servers are outside tools that Claude Code connects to. When one of them reports an error, Claude Code redacts the message, meaning it hides any text that came from your configuration (where secrets such as keys can live). That redaction now has an overall limit on how much decoding work it does and how many repeats it will handle. If an error message repeats too much of the configuration, Claude Code reports \"MCP error text repeats too much of the config\". The checking itself was also reworked to scan the text in a single pass.\n\nBefore this change, there was a simpler limit on decoding work.\n\n**Why**\n\nThis protects Claude Code against unusual or deliberately strange error messages that could otherwise make the redaction step take a very long time.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}