{"version":"2.1.277","anchor":"tool-execution-errortelemetry-logs-now-redact-tool-names-an","canonical_anchor":"tool-execution-errortelemetry-logs-now-redact-tool-names-an","heading":"Tool-execution error\/telemetry logs now redact tool names and truncate error content by structure, not raw text","tier":"notice","area":"Tool Validation","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/tool-execution-errortelemetry-logs-now-redact-tool-names-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Tool-execution error\/telemetry logs now redact tool names and truncate error content by structure, not raw text\n\nTool error and permission-denial debug logs now report structured metadata instead of raw tool names and text snippets\n\n**What**\n\nLocal debug log lines for tool input validation errors, validate-input rejections, permission denials, and runtime tool errors no longer include a raw slice of the offending input, message, or error text. Instead they report structured details: issue codes, byte\/character counts, and error codes. These log lines also now use a new classifier that labels skill tools, MCP tools, and dynamically-named tools with a generic label like `skill_tool`, `mcp_tool`, or `dynamic_tool` instead of printing the tool's literal name.\n\n**Why**\n\nThis keeps potentially sensitive tool names and raw error content out of debug logs while still giving useful, structured information for diagnosing tool failures.\n\n- Area: Tool Validation\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}