{"version":"2.1.269","anchor":"new-plugin-hook-op-toolcheck-lets-a-plugin-test-a-tool-c","canonical_anchor":"new-plugin-hook-op-toolcheck-lets-a-plugin-test-a-tool-c","heading":"New plugin hook op: $.tool.check lets a plugin test a tool call without running it","tier":"use","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-plugin-hook-op-toolcheck-lets-a-plugin-test-a-tool-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New plugin hook op: $.tool.check lets a plugin test a tool call without running it\n\nNew plugin hook lets a plugin check whether a tool call would be allowed without actually running it\n\n**What**\n\nPlugins (add-on scripts that can hook into Claude Code's behavior) can now call a new `$.tool.check` operation. Given a tool name and its input, this runs the same permission and argument checks Claude Code would normally run before executing that tool, and returns the verdict (allowed, denied, etc.) without actually running the tool. It's also wired into the tool-call hook used by the Claude Code SDK, which now validates the tool name and input before dispatching to this new check.\n\n**Why**\n\nThis lets a plugin or SDK integration preview whether a tool call would be permitted, useful for building custom approval flows or diagnostics without side effects from actually running the tool.\n\n- Area: Plugin Hooks\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}