release_machine
Delete an always-on machine. DESTRUCTIVE AND IMMEDIATE: stops billing, takes a last backup and destroys the VM — there is no grace period and no undo. The backup is kept 7 days and is the only way back: list_backups, then restore_machine_from_backup onto a new machine. Requires confirm:true. Owne...
This record as markdown: /tools/cloud-easybits-easybits/release-machine.md
What release_machine does on EasyBits
AI agents call release_machine 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 release_machine is rated Critical
Permanently deletes virtual machines with no recovery except 7-day backups; irreversible destructive action.
From the tool's definition Delete, destroys the VM, no undo, irreversible action.
Attacks that exploit this kind of access
The rule that runs release_machine 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 release_machine, this is the rule to start with:
release_machine 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 release_machine call is checked against it from then on.
Questions about release_machine
Delete an always-on machine. DESTRUCTIVE AND IMMEDIATE: stops billing, takes a last backup and destroys the VM — there is no grace period and no undo. The backup is kept 7 days and is the only way back: list_backups, then restore_machine_from_backup onto a new machine. Requires confirm:true. Owner-only. 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 release_machine: 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.
release_machine 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 release_machine 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 release_machine. 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.
release_machine 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