{"version":"2.1.323","anchor":"bridge-tool-use-lookup-verifies-tool-name","canonical_anchor":"bridge-tool-use-lookup-verifies-tool-name","heading":"Approval lookups now check the tool call matches the tool on the approval card","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bridge-tool-use-lookup-verifies-tool-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Approval lookups now check the tool call matches the tool on the approval card\n\nWhen Claude Code looks up a pending approval in the transcript, the tool call it finds must match the tool named on the stored card\n\n**What**\n\nA tool call is one action Claude takes, such as running a command or editing a file. Some tool calls wait for your approval, and Claude Code stores a card describing each one. When Claude Code goes back to the session transcript to find the tool call behind a card, it now checks that the call it finds uses the tool the card names.\n\nIf the tool does not match, Claude Code treats the call as not found and logs a warning. Before, any tool call with the matching ID was accepted.\n\n**Why**\n\nAn approval can no longer be applied to a tool call that is not the one you were asked about.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}