hooks_worker-dispatch · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What hooks_worker-dispatch does on Claude Flow

AI agents invoke hooks_worker-dispatch 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 IT NEEDS A POLICY

Why hooks_worker-dispatch needs a policy

The tool dispatches background workers to execute analysis and optimization tasks. This falls squarely in the Execute category as it triggers external operations (worker processes) whose effects depend on arguments.

From the tool's definition "Dispatch a background worker for analysis/optimization tasks" — dispatches background workers that run tasks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_worker-dispatch Rate-limited

hooks_worker-dispatch 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_worker-dispatch": {
      "limits": [
        {
          "counter": "hooks_worker-dispatch_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about hooks_worker-dispatch

What does the hooks_worker-dispatch tool do? +

Dispatch a background worker for analysis/optimization tasks 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.

How do I enforce a policy on hooks_worker-dispatch? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_worker-dispatch: 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_worker-dispatch? +

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

Can I rate-limit hooks_worker-dispatch? +

Yes. Add a rate_limit block to the hooks_worker-dispatch 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_worker-dispatch completely? +

Set action: deny in the PolicyLayer policy for hooks_worker-dispatch. 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_worker-dispatch? +

hooks_worker-dispatch 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.