Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

New tool.check hook event wired into the tool-approval pipeline

New tool.check hook can override a hook's earlier 'deny' decision on a tool call

TierUse it nowhow much it should matter to you
Useful4my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaPlugin Hookswhat it touches
KindNew Featuresin v2.1.269,
Use it now Notable No documentation found

New tool.check hook can override a hook's earlier 'deny' decision on a tool call

What

A new hook and plugin event called tool.check has joined the existing tool.call and tool.describe events. It has its own restore, check, and settle logic, and is now invoked from the main tool-approval flow specifically when an earlier hook decision was to deny a tool call. This gives a tool.check hook or plugin the chance to override that denial to allow or ask instead, before the request falls through to the normal classifier.

Why

This gives plugin authors a way to intervene late in the tool-approval process and reverse a denial, adding more flexibility to how tool permissions are decided.

Read from
Names in the bundletool.check
What the documentation says
tool.call Monitoring modified, high confidence | `gen_ai.tool.call.id` | Same value as `tool_use_id`. OpenTelemetry GenAI semantic convention | | see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreestool.call on Monitoring

See this entry in the whole of v2.1.269 →

Feedback