{"version":"2.1.323","anchor":"approval-that-rewrites-tool-input-is-denied-for-whole-input","canonical_anchor":"approval-that-rewrites-tool-input-is-denied-for-whole-input","heading":"Approvals that change a tool's input after you saw it are now refused","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/approval-that-rewrites-tool-input-is-denied-for-whole-input","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Approvals that change a tool's input after you saw it are now refused\n\nIf an approval comes back with different tool input than you were shown, Claude Code now refuses the call and asks again\n\n**What**\n\nA tool call is a single action Claude takes, such as editing a file. Some tools ask you to approve the whole input before they run. For those tools, Claude Code now compares the input in the approval with the input you were shown.\n\nIf they differ, nothing runs. Claude is told that the approval came back with different arguments and that it should call the tool again so you are asked again.\n\nBefore, only the list of files in the input was compared.\n\n**Why**\n\nAn approval can no longer quietly change what a tool does after you agreed to it. If something alters the input on the way, the call fails openly and you get a fresh prompt for what will actually run.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}