{"version":"2.1.268","anchor":"mcp-claudeai-proxy-401-telemetry-now-sanitizes-the-proxy-err","canonical_anchor":"mcp-claudeai-proxy-401-telemetry-now-sanitizes-the-proxy-err","heading":"MCP claudeai-proxy 401 telemetry now sanitizes the proxy error code","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-claudeai-proxy-401-telemetry-now-sanitizes-the-proxy-err","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP claudeai-proxy 401 telemetry now sanitizes the proxy error code\n\nMCP proxy 401 telemetry now sanitizes the error code before logging it\n\n**What**\n\nWhen the `tengu_mcp_claudeai_proxy_401` telemetry event records a `proxyErrorCode`, that value is now passed through a validator that only allows codes matching a simple letters\/numbers\/underscore\/hyphen pattern starting with a letter. Any code that doesn't match is reported as `\"nonconforming\"` instead of being logged raw.\n\n**Why**\n\nThis prevents arbitrary or malformed error code strings from being logged verbatim in telemetry, keeping the recorded data predictable and safe.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}