{"version":"2.1.296","anchor":"tool-denial-monitor-marker-and-a-new-denial-kind","canonical_anchor":"tool-denial-monitor-marker-and-a-new-denial-kind","heading":"Changes to how blocked tool actions are marked and shown","tier":"notice","area":"Tool Calls","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/tool-denial-monitor-marker-and-a-new-denial-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Changes to how blocked tool actions are marked and shown\n\nTool results can now be marked as blocked by a denial check, and a new \"model not current\" denial reason was added\n\n**Unclear.** What the new `model_not_current` reason is used for is not known.\n\n**What**\n\nA tool call is an action Claude asks Claude Code to take, such as running a command. Changes to how refused tool calls are handled:\n\n- Tool results can carry a mark saying a denial check blocked them, and the result shown on screen updates when that mark changes.\n\n- A subagent, a helper Claude starts to work on part of a task, can have its tool results blanked out.\n\n- A new reason, `model_not_current`, joins reasons such as `blocked_by_hook`, `check_failed` and `auth_failed`.\n\n**Why**\n\nThese relate to how Claude Code handles and shows actions that were refused.\n\n- Area: Tool Calls\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}