hooks_pre-command · Ruflo MCP: Risk & Policy

WHAT IT DOES

What hooks_pre-command does on Ruflo

AI agents invoke hooks_pre-command to trigger actions in Ruflo. 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 IT NEEDS A POLICY

Why hooks_pre-command needs a policy

This tool intercepts and evaluates commands before they are executed via Bash hooks. While framed as a risk assessment step, it operates in the execution pipeline for shell commands, meaning it is tightly coupled to command execution flows. Misuse or bypass could allow arbitrary command execution through the hook mechanism.

From the tool's definition 'Assess risk before executing a command' and 'native Bash hooks (via Claude Code'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_pre-command Rate-limited

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.

View as policy code

policy.json

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

RATE-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_pre-command

What does the hooks_pre-command tool do? +

Assess risk before executing a command Use when native Bash hooks (via Claude Code\. It is categorised as a Execute tool in the Ruflo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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

Register the Ruflo 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 Ruflo. Nothing to install.

What risk level is hooks_pre-command? +

hooks_pre-command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hooks_pre-command? +

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.

How do I block hooks_pre-command completely? +

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.

What MCP server provides hooks_pre-command? +

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

// THE FULL RECORD

hooks_pre-command is one line of Ruflo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →