hooks_route

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/hooks-route.md

WHAT IT DOES

What hooks_route does on Claude Flow

AI agents call hooks_route to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why hooks_route is rated Low

This tool purely retrieves a routing recommendation (which model/tier to use for a task). It reads/analyzes the task and returns a suggestion with no side effects, no data modification, no execution of code, and no financial implications.

From the tool's definition Get a 3-tier routing recommendation for a task... Returns the recommended model

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hooks_route safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_route, this is the rule to start with:

hooks_route Allowed

hooks_route is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_route": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hooks_route call is checked against it from then on.

FAQ

Questions about hooks_route

What does the hooks_route tool do? +

Get a 3-tier routing recommendation for a task: Tier 1 (deterministic codemod, ~0ms / $0 — for var-to-const, remove-console, add-logging), Tier 2 (Haiku — simple), Tier 3 (Sonnet/Opus — complex). Use this BEFORE spawning an agent to avoid sending simple transforms to Sonnet. Native tools have no equivalent — Claude Code does not introspect its own model-selection cost. Returns the recommended model + a. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hooks_route? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_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_route? +

hooks_route is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hooks_route? +

Yes. Add a rate_limit block to the hooks_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_route completely? +

Set action: deny in the PolicyLayer policy for hooks_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_route? +

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

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →