hooks_post-command · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What hooks_post-command does on Claude Flow

AI agents use hooks_post-command to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.

WHY IT NEEDS A POLICY

Why hooks_post-command needs a policy

This tool creates or modifies records of command execution outcomes, which is a reversible write operation. It does not execute commands itself (Execute category) nor delete data (Destructive). Severity is medium because malicious recording could falsify audit logs or create misleading execution records in an enterprise system, but the primary impact is data modification rather than direct system compromise.

From the tool's definition Tool name 'hooks_post-command' and description 'Record command execution outcome' indicate it writes/records data about executed commands. The incomplete description mentions 'native Bash hooks' suggesting integration with command execution pipelines.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_post-command Rate-limited

hooks_post-command stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_post-command": {
      "limits": [
        {
          "counter": "hooks_post-command_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about hooks_post-command

What does the hooks_post-command tool do? +

Record command execution outcome Use when native Bash hooks (via Claude Code\. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on hooks_post-command? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_post-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.

What risk level is hooks_post-command? +

hooks_post-command is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hooks_post-command? +

Yes. Add a rate_limit block to the hooks_post-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.

How do I block hooks_post-command completely? +

Set action: deny in the PolicyLayer policy for hooks_post-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.

What MCP server provides hooks_post-command? +

hooks_post-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.