sandbox_fork
Boot N copy-on-write children from a sandbox (fresh IP each, collision-free), to explore variations in parallel. Pass sandboxId to snapshot a live box then fork it (Morph-style branch), OR snapshotId to fork an existing snapshot. count 1–16 (default 1). Children are ephemeral (auto-reaped at TTL)...
This record as markdown: /tools/cloud-easybits-easybits/sandbox-fork.md
What sandbox_fork does on EasyBits
AI agents invoke sandbox_fork to trigger actions in EasyBits. 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 sandbox_fork is rated High
Spawns multiple live sandbox environments consuming resources and executing arbitrary workloads.
From the tool's definition Boot N copy-on-write children from a sandbox, explore variations in parallel
Attacks that exploit this kind of access
The rule that runs sandbox_fork safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_fork, this is the rule to start with:
sandbox_fork 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 EasyBits, apply this rule, and every sandbox_fork call is checked against it from then on.
Questions about sandbox_fork
Boot N copy-on-write children from a sandbox (fresh IP each, collision-free), to explore variations in parallel. Pass sandboxId to snapshot a live box then fork it (Morph-style branch), OR snapshotId to fork an existing snapshot. count 1–16 (default 1). Children are ephemeral (auto-reaped at TTL) and count against your concurrent-sandbox budget. Returns the child records (still starting — poll sandbox_status until running). It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_fork: 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 EasyBits. Nothing to install.
sandbox_fork 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 sandbox_fork 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 sandbox_fork. 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.
sandbox_fork is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue