coordination_orchestrate
Orchestrate multi-agent coordination Use when native Task is wrong because the work crosses multiple agents that need to vote/sync/load-balance — TodoWrite + a single Task cannot orchestrate consensus. For one-off subtask dispatch, native Task is fine.
This record as markdown: /tools/io-github-ruvnet-claude-flow/coordination-orchestrate.md
What coordination_orchestrate does on Claude Flow
AI agents invoke coordination_orchestrate 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 coordination_orchestrate is rated High
This tool executes coordination logic across multiple AI agents, triggering consensus protocols, synchronization, and load balancing. It is not merely reading or writing data — it actively drives agent behavior and dispatches work across a distributed system. Misuse could cause cascading effects across all orchestrated agents, leading to high blast radius.
From the tool's definition "Orchestrate multi-agent coordination" with agents that "vote/sync/load-balance" — triggers external operations across multiple agents
Attacks that exploit this kind of access
The rule that runs coordination_orchestrate 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 coordination_orchestrate, this is the rule to start with:
coordination_orchestrate 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every coordination_orchestrate call is checked against it from then on.
Questions about coordination_orchestrate
Orchestrate multi-agent coordination Use when native Task is wrong because the work crosses multiple agents that need to vote/sync/load-balance — TodoWrite + a single Task cannot orchestrate consensus. For one-off subtask dispatch, native Task is fine. 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.
Register the Claude Flow MCP server in PolicyLayer and add a rule for coordination_orchestrate: 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.
coordination_orchestrate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the coordination_orchestrate 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.
Set action: deny in the PolicyLayer policy for coordination_orchestrate. 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.
coordination_orchestrate 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.
More on Claude Flow, and thousands of servers like it.
Across the catalogue