{"version":"2.1.289","anchor":"toolcheck-plugin-hook-can-be-floored-for-pretooluse-asks","canonical_anchor":"toolcheck-plugin-hook-can-be-floored-for-pretooluse-asks","heading":"Plugin tool.check hooks get an extra input when a PreToolUse hook asks for permission","tier":"internal","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/toolcheck-plugin-hook-can-be-floored-for-pretooluse-asks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Plugin `tool.check` hooks get an extra input when a PreToolUse hook asks for permission\n\nWhen a PreToolUse hook has asked for permission, plugin tool checks are now built with that hook's ask passed in as an extra input\n\n**Unclear.** What the plugin check does with the hook's ask is not clear.\n\n**What**\n\nPlugins can define a `tool.check` hook, a piece of plugin code that looks at a tool call before it runs. A tool call is Claude Code using one of its tools, such as running a shell command or editing a file. When a `PreToolUse` hook has asked for permission, Claude Code now builds the plugin's `tool.check` with that ask passed in as an extra input. A `PreToolUse` hook is a hook that runs before a tool call executes and can block it. Previously the check was built without this input.\n\n**Why**\n\nThis changes how plugin tool checks and permission requests from hooks fit together. If you use both, a plugin's check can now be affected by an earlier hook's request to ask you first.\n\n- Area: Plugin Hooks\n- Names: `tool.check`, `PreToolUse`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}