hooks_coverage-route · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What hooks_coverage-route does on Claude Flow

AI agents invoke hooks_coverage-route 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_coverage-route needs a policy

This tool triggers routing of tasks to agents, which constitutes executing an external operation (dispatching work to agent processes). It does not merely read data — it actively directs tasks to agents based on coverage analysis. The 'ruvector integration' suggests it interfaces with an external system.

From the tool's definition Route task to agents based on test coverage gaps (ruvector integration)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_coverage-route Rate-limited

hooks_coverage-route 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_coverage-route": {
      "limits": [
        {
          "counter": "hooks_coverage-route_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_coverage-route

What does the hooks_coverage-route tool do? +

Route task to agents based on test coverage gaps (ruvector integration). 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_coverage-route? +

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

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

Can I rate-limit hooks_coverage-route? +

Yes. Add a rate_limit block to the hooks_coverage-route 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_coverage-route completely? +

Set action: deny in the PolicyLayer policy for hooks_coverage-route. 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_coverage-route? +

hooks_coverage-route 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.