agent_run_destroy

Destroy the sandbox underlying an agent run. Call this after you

SERVEREasyBits SOURCE@easybits.cloud/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/agent-run-destroy.md

WHAT IT DOES

What agent_run_destroy does on EasyBits

AI agents call agent_run_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.

RISK

Why agent_run_destroy is rated Critical

Irreversibly destroys persistent microVM infrastructure; cannot be undone.

From the tool's definition Destroy the sandbox underlying an agent run.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_run_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 agent_run_destroy, this is the rule to start with:

agent_run_destroy Hidden

agent_run_destroy is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "agent_run_destroy"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every agent_run_destroy call is checked against it from then on.

FAQ

Questions about agent_run_destroy

What does the agent_run_destroy tool do? +

Destroy the sandbox underlying an agent run. Call this after you. 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.

How do I enforce a policy on agent_run_destroy? +

Register the EasyBits MCP server in PolicyLayer and add a rule for agent_run_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.

What risk level is agent_run_destroy? +

agent_run_destroy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit agent_run_destroy? +

Yes. Add a rate_limit block to the agent_run_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.

How do I block agent_run_destroy completely? +

Set action: deny in the PolicyLayer policy for agent_run_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.

What MCP server provides agent_run_destroy? +

agent_run_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.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →