Spawn claude-ide-bridge for a workspace dir. Returns pid/port/authToken once lock appears; optionally waits for extension handshake.
AI agents invoke spawnWorkspace to trigger actions in Patchwork Os. 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.
The tool spawns a new process (claude-ide-bridge), which is an external process execution. It returns sensitive credentials (authToken) and a port, meaning misuse could expose authentication tokens or create unauthorized bridge processes. This clearly falls under Execute as it triggers an external operation/process launch.
From the tool's definition Spawn claude-ide-bridge for a workspace dir. Returns pid/port/authToken once lock appears; optionally waits for extension handshake.
Documented attack patterns abuse exactly the kind of access spawnWorkspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Patchwork Os, and nothing reaches the server without passing your rules. This is the rule we recommend for spawnWorkspace:
{
"version": "1",
"default": "deny",
"tools": {
"spawnWorkspace": {
"limits": [
{
"counter": "spawnworkspace_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}spawnWorkspace 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 claude-ide-bridge for a workspace dir. Returns pid/port/authToken once lock appears; optionally waits for extension handshake. It is categorised as a Execute tool in the Patchwork Os MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Patchwork Os MCP server in PolicyLayer and add a rule for spawnWorkspace: 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 Patchwork Os. Nothing to install.
spawnWorkspace 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 spawnWorkspace 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 spawnWorkspace. 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.
spawnWorkspace is provided by the Patchwork Os MCP server (oolab-labs/patchwork-os). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Patchwork Os, 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.
11 Patchwork Os tools catalogued and risk-classified — across an index of 43,000+ MCP servers.