sandbox_exec_background
Start a long-running command in the background. Returns { execId, status } immediately instead of blocking like sandbox_exec. Poll with sandbox_exec_status; list with sandbox_exec_list; stop with sandbox_exec_kill. Use for dev servers / long tasks — pair with sandbox_expose_port to reach a server...
This record as markdown: /tools/cloud-easybits-easybits/sandbox-exec-background.md
What sandbox_exec_background does on EasyBits
AI agents invoke sandbox_exec_background 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_exec_background is rated High
Executes arbitrary Linux commands with root access in persistent microVMs, enabling code execution with wide blast radius.
From the tool's definition Start long-running command in background; executes arbitrary shell commands with root.
Attacks that exploit this kind of access
The rule that runs sandbox_exec_background 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_exec_background, this is the rule to start with:
sandbox_exec_background 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_exec_background call is checked against it from then on.
Questions about sandbox_exec_background
Start a long-running command in the background. Returns { execId, status } immediately instead of blocking like sandbox_exec. Poll with sandbox_exec_status; list with sandbox_exec_list; stop with sandbox_exec_kill. Use for dev servers / long tasks — pair with sandbox_expose_port to reach a server it starts. Do NOT try to background a command inside sandbox_exec with nohup or &: sandbox_exec is a synchronous call and its shell dies with the response, taking the child with it. Prefer writing the command as. 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_exec_background: 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_exec_background 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_exec_background 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_exec_background. 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_exec_background 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