What probably matters to youSection of the release
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.
tool.callMonitoringmodified, high confidence| `gen_ai.tool.call.id` | Same value as `tool_use_id`. OpenTelemetry GenAI semantic convention | |see the edit
Since it was published
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up tool.check, on Configure permissions.That precedence covers hooks in settings files and in a plugin's `hooks/hooks.json`. A [mod](/docs/en/plugins/mods/overview) you install that hooks `tool.check` answers after the rules and the `PreToolUse` hooks have decided, and its answe…permissionssee the edit
Added sinceA small documentation edit on Automate actions with hooks touched a line naming tool.check after this was published.A [mod](/docs/en/plugins/mods/overview) you install that hooks `tool.check` can approve a call that your `PreToolUse` hook blocked, unless the hook is in managed settings. [Extend permissions with hooks](/docs/en/permissions#extend-permiss…hooks-guidesee 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
