teammate_spawn
Spawn a new teammate in a team. Returns AgentInput for Claude Code Task tool.
This record as markdown: /tools/io-github-ruvnet-claude-flow/teammate-spawn.md
What teammate_spawn does on Claude Flow
AI agents invoke teammate_spawn 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 teammate_spawn is rated High
Spawning a new agent/teammate is an Execute-category action because it instantiates and starts a new running process or agent with its own execution context. Given this is part of an AI orchestration platform with 'hive-mind swarms' and code execution capabilities, a misused spawn could launch unauthorized agents performing arbitrary actions, making severity high.
From the tool's definition 'Spawn a new teammate in a team' — creates and launches a new agent/process instance; 'Returns AgentInput for Claude Code Task tool' indicates it triggers execution of an agent capable of running code tasks
Attacks that exploit this kind of access
The rule that runs teammate_spawn 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 teammate_spawn, this is the rule to start with:
teammate_spawn 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 teammate_spawn call is checked against it from then on.
Questions about teammate_spawn
Spawn a new teammate in a team. Returns AgentInput for Claude Code Task tool. 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 teammate_spawn: 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.
teammate_spawn 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 teammate_spawn 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 teammate_spawn. 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.
teammate_spawn 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