This record as markdown: /tools/io-github-ruvnet-claude-flow/task-orchestrate.md
What task_orchestrate does on Claude Flow
AI agents invoke task_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 task_orchestrate is rated High
Task orchestration in an AI hive-mind context implies spawning agents, dispatching subtasks, and triggering external operations dynamically. The description is vague but in the context of 87 MCP tools, agent spawning, and swarm coordination, misuse could cascade across many systems. Classified as Execute due to runtime dispatch semantics; severity is high given the blast radius of orchestrating multi-agent workflows.
From the tool's definition "Orchestrate a task" — triggers execution and coordination of operations across agents/tools
Attacks that exploit this kind of access
The rule that runs task_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 task_orchestrate, this is the rule to start with:
task_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 task_orchestrate call is checked against it from then on.
Questions about task_orchestrate
Orchestrate a task. 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 task_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.
task_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 task_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 task_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.
task_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