teammate_batch_route · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What teammate_batch_route does on Claude Flow

AI agents invoke teammate_batch_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 teammate_batch_route needs a policy

Routing tasks to teammates is an orchestration/dispatch action that triggers downstream operations. It is not a simple read or write, but an execution of task distribution logic with side effects dependent on what tasks are routed. The 'optimally, avoiding over-assignment' qualifier suggests runtime scheduling decisions with real consequences, but no indication of irreversible destruction or financial impact.

From the tool's definition 'Route multiple tasks to teammates' — dispatches work items to agents/teammates, triggering external operations whose effects depend on the tasks and routing logic.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teammate_batch_route Rate-limited

teammate_batch_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": {
    "teammate_batch_route": {
      "limits": [
        {
          "counter": "teammate_batch_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 teammate_batch_route

What does the teammate_batch_route tool do? +

Route multiple tasks to teammates optimally, avoiding over-assignment. 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 teammate_batch_route? +

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

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

Can I rate-limit teammate_batch_route? +

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

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

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