AI agents invoke spawn to trigger actions in Async Bash. 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.
Despite the empty description, the server's explicit purpose is spawning and managing bash commands. 'spawn' is a sibling to 'list_processes' and 'poll', forming a classic spawn/monitor pattern for async shell execution. Spawning arbitrary shell commands is an Execute-category action with critical severity, as an AI agent could run any system command with potentially irreversible or destructive consequences.
From the tool's definition Tool name 'spawn' on a server described as 'spawning and managing bash commands asynchronously' and 'Run multiple shell commands in parallel'. The server context makes clear this tool spawns shell commands.
Documented attack patterns abuse exactly the kind of access spawn gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Async Bash, and nothing reaches the server without passing your rules. This is the rule we recommend for spawn:
{
"version": "1",
"default": "deny",
"tools": {
"spawn": {
"limits": [
{
"counter": "spawn_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
spawn. It is categorised as a Execute tool in the Async Bash MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Async Bash MCP server in PolicyLayer and add a rule for 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 Async Bash. Nothing to install.
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 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 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.
spawn is provided by the Async Bash MCP server (xhuw/async-bash-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Async Bash, 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.
3 Async Bash tools catalogued and risk-classified — across an index of 43,000+ MCP servers.