teammate_spawn_team
Create a new team for multi-agent collaboration using native TeammateTool.
This record as markdown: /tools/ruflo/teammate-spawn-team.md
What teammate_spawn_team does on Ruflo
AI agents use teammate_spawn_team to create or update resources in Ruflo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.
Why teammate_spawn_team is rated Medium
This tool creates a new team entity (a Write operation). However, severity is high because spawning multi-agent teams in a swarm orchestration system can trigger cascading autonomous workflows, resource consumption, and difficult-to-reverse coordination side effects — even if the immediate action is a reversible resource creation.
From the tool's definition "Create a new team for multi-agent collaboration using native TeammateTool"
Attacks that exploit this kind of access
The rule that runs teammate_spawn_team safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teammate_spawn_team, this is the rule to start with:
teammate_spawn_team stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every teammate_spawn_team call is checked against it from then on.
Questions about teammate_spawn_team
Create a new team for multi-agent collaboration using native TeammateTool. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ruflo MCP server in PolicyLayer and add a rule for teammate_spawn_team: 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 Ruflo. Nothing to install.
teammate_spawn_team is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the teammate_spawn_team 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_team. 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_team is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue