{"version":"2.1.224","anchor":"auto-mode-telemetry-records-whether-the-tool-was-mcp","canonical_anchor":"auto-mode-telemetry-records-whether-the-tool-was-mcp","heading":"Auto-mode telemetry records whether the tool was MCP","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/auto-mode-telemetry-records-whether-the-tool-was-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Auto-mode telemetry records whether the tool was MCP\n\nMore auto-mode permission events record whether the tool was from an MCP server.\n\n**What**\n\nAuto-mode decision, fallback-to-ask and denial-limit events now carry a flag saying whether the tool came from an MCP server, defaulting to false, alongside the existing tool name and denial counts.\n\n**Evidence**\n\n`tengu_auto_mode_denial_limit_exceeded`, `tengu_auto_mode_fallback_to_ask`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}