This record as markdown: /tools/cloud-easybits-easybits/agent-destroy.md
What agent_destroy does on EasyBits
AI agents call agent_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 agent_destroy is rated Critical
Permanently deletes a running microVM and all associated state without recovery option.
From the tool's definition Destroy a persistent agent; irreversibly removes running microVM.
Attacks that exploit this kind of access
The rule that runs agent_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_destroy, this is the rule to start with:
agent_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 agent_destroy call is checked against it from then on.
Questions about agent_destroy
Destroy a persistent agent created via. 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 agent_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.
agent_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 agent_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 agent_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.
agent_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