{"version":"2.1.268","anchor":"auto-mode-permission-telemetry-now-tags-mcp-tool-calls-with","canonical_anchor":"auto-mode-permission-telemetry-now-tags-mcp-tool-calls-with","heading":"Auto-mode permission telemetry now tags MCP tool calls with connection\/ambiguity info","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/auto-mode-permission-telemetry-now-tags-mcp-tool-calls-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Auto-mode permission telemetry now tags MCP tool calls with connection\/ambiguity info\n\nAuto-mode telemetry now tags MCP tool calls with which server they connect to and whether that's ambiguous\n\n**What**\n\nWhen Claude Code's auto-mode (a mode that can approve or reject tool calls automatically) logs telemetry about falling back to asking the user, making a decision, or showing a permission prompt, calls involving an MCP tool (one provided by a Model Context Protocol server) now get extra information attached: which server connection the tool belongs to, and a flag for whether that association is ambiguous. This is computed only when needed and reused for the rest of that call.\n\n**Why**\n\nThis gives clearer visibility into how auto-mode handles MCP tools specifically, which is useful since a tool name alone doesn't always identify which server it came from.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}