AI agents invoke spawn_workers to trigger actions in Claude Team MCP Server. 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.
Based on the server description, spawning workers creates new Claude Code sessions in iTerm2 terminal windows, which is an Execute-level action as it triggers external processes/operations.
From the tool's definition Tool name 'spawn_workers' on a server that 'spawns, monitors, and messages worker sessions' in iTerm2 terminal windows with git worktree management
Documented attack patterns abuse exactly the kind of access spawn_workers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Team MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for spawn_workers:
{
"version": "1",
"default": "deny",
"tools": {
"spawn_workers": {
"limits": [
{
"counter": "spawn_workers_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}spawn_workers 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.
Free to start. No card required.
spawn_workers. It is categorised as a Execute tool in the Claude Team MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Team MCP Server MCP server in PolicyLayer and add a rule for spawn_workers: 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 Team MCP Server. Nothing to install.
spawn_workers 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 spawn_workers 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 spawn_workers. 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.
spawn_workers is provided by the Claude Team MCP Server MCP server (martian-engineering/maniple). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Team MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Claude Team MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.