{"version":"2.1.224","anchor":"mcp-tools-that-need-you-to-click-through-are-not-silently-pr","canonical_anchor":"mcp-tools-that-need-you-to-click-through-are-not-silently-pr","heading":"MCP tools that need you to click through are not silently pre-approved","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/mcp-tools-that-need-you-to-click-through-are-not-silently-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### MCP tools that need you to click through are not silently pre-approved\n\nMCP tools that need you to click through always reach you instead of being auto-approved.\n\n**What**\n\nAn MCP tool that declares it requires user interaction no longer has its permission re-checked in the background and auto-proceeded when the check returns \"allow\". Those tools always reach you.\n\n**Details**\n\n- The background re-check bails out when the tool reports `requiresUserInteraction`, which comes from the MCP metadata key `anthropic\/requiresUserInteraction`.\n- Separately, the permission-prompt telemetry event now records `isMcp`, distinguishing MCP tools from built-in ones.\n\n**Evidence**\n\n`anthropic\/requiresUserInteraction`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 3\/5"}