{"version":"2.1.269","anchor":"new-toolcheck-hook-event-wired-into-the-tool-approval-pip","canonical_anchor":"new-toolcheck-hook-event-wired-into-the-tool-approval-pip","heading":"New tool.check hook event wired into the tool-approval pipeline","tier":"use","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-toolcheck-hook-event-wired-into-the-tool-approval-pip","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New `tool.check` hook event wired into the tool-approval pipeline\n\nNew tool.check hook can override a hook's earlier 'deny' decision on a tool call\n\n**What**\n\nA 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.\n\n**Why**\n\nThis 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.\n\n- Area: Plugin Hooks\n- Names: `tool.check`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}