hooks_post-command · Ruflo MCP: Risk & Policy

WHAT IT DOES

What hooks_post-command does on Ruflo

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

WHY IT NEEDS A POLICY

Why hooks_post-command needs a policy

This tool writes/records data about command outcomes (logs, records, or state updates). It is not destructive (no deletion), not financial, and not directly executing commands itself—it captures the results of execution. The medium severity reflects that while it modifies state by recording outcomes, the impact is limited to logging/recording rather than altering primary application data or infrastructure.

From the tool's definition Tool name 'hooks_post-command' and description 'Record command execution outcome' indicates creating or logging records of command execution events. The description mentions 'Bash hooks (via Claude Code' suggesting integration with command execution systems.

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 Ruflo, 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 Ruflo 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 Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.