hooks_pre-command
Assess risk before executing a command Use when native Bash hooks (via Claude Code\
This record as markdown: /tools/io-github-ruvnet-claude-flow/hooks-pre-command.md
What hooks_pre-command does on Claude Flow
AI agents invoke hooks_pre-command to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why hooks_pre-command is rated High
This tool sits in the command execution lifecycle, intercepting commands before they run via Bash hooks. While its stated purpose is risk assessment (a Read-like activity), it operates within an Execute context — hooking into command pipelines. Misuse or misconfiguration could suppress risk warnings, allow dangerous commands to proceed, or be abused to manipulate what commands are deemed safe.
From the tool's definition 'Assess risk before executing a command' and 'Bash hooks' — the tool is triggered in the execution pipeline of commands, acting as a pre-execution interceptor for Bash operations
Attacks that exploit this kind of access
The rule that runs hooks_pre-command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_pre-command, this is the rule to start with:
hooks_pre-command stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hooks_pre-command call is checked against it from then on.
Questions about hooks_pre-command
Assess risk before executing a command Use when native Bash hooks (via Claude Code\. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_pre-command: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Flow. Nothing to install.
hooks_pre-command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hooks_pre-command rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for hooks_pre-command. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
hooks_pre-command is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
Across the catalogue