sandbox_suspend
Snapshot a sandbox to disk and free its CPU/IP — the box stops billing compute but keeps its state. The TTL is PAUSED while suspended: the remaining lifetime is saved and restored on sandbox_resume, so you do NOT need to call sandbox_extend afterward. Restore with sandbox_resume.
This record as markdown: /tools/cloud-easybits-easybits/sandbox-suspend.md
What sandbox_suspend does on EasyBits
AI agents use sandbox_suspend to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why sandbox_suspend is rated Medium
Modifies sandbox state reversibly via snapshot; no deletion or execution, but affects system resources and billing.
From the tool's definition Snapshot sandbox to disk, free CPU/IP, stop billing, pauses TTL.
Attacks that exploit this kind of access
The rule that runs sandbox_suspend 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_suspend, this is the rule to start with:
sandbox_suspend stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_suspend call is checked against it from then on.
Questions about sandbox_suspend
Snapshot a sandbox to disk and free its CPU/IP — the box stops billing compute but keeps its state. The TTL is PAUSED while suspended: the remaining lifetime is saved and restored on sandbox_resume, so you do NOT need to call sandbox_extend afterward. Restore with sandbox_resume. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_suspend: 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_suspend is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sandbox_suspend 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_suspend. 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_suspend 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.
This server
Across the catalogue