sandbox_destroy
Permanently destroy an EPHEMERAL sandbox and free its resources. Idempotent. (Permanent machines are released via release_machine, which soft-deletes.)
This record as markdown: /tools/cloud-easybits-easybits/sandbox-destroy.md
What sandbox_destroy does on EasyBits
AI agents call sandbox_destroy to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why sandbox_destroy is rated Critical
Irreversibly deletes a sandbox environment and cannot be undone without recreation.
From the tool's definition Permanently destroy an EPHEMERAL sandbox and free its resources.
Attacks that exploit this kind of access
The rule that runs sandbox_destroy 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_destroy, this is the rule to start with:
sandbox_destroy is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every sandbox_destroy call is checked against it from then on.
Questions about sandbox_destroy
Permanently destroy an EPHEMERAL sandbox and free its resources. Idempotent. (Permanent machines are released via release_machine, which soft-deletes.). It is categorised as a Destructive tool in the EasyBits MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_destroy: 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_destroy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sandbox_destroy 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_destroy. 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_destroy 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