Destroy a specific VM. Args: vm_id: ID of the VM to destroy Returns: Destruction result
AI agents call destroy_vm to permanently remove resources in Ludus FastMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly destroys a VM by ID, which is an irreversible operation that permanently removes infrastructure. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius depends on what the VM contained and the agent's access to vm_ids, unauthorized destruction of infrastructure in a cyber range could disrupt testing…
From the tool's definition Tool name 'destroy_vm' and description 'Destroy a specific VM' indicate irreversible deletion. The action cannot be undone and results in loss of the VM and its associated data.
Documented attack patterns abuse exactly the kind of access destroy_vm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for destroy_vm:
{
"version": "1",
"default": "deny",
"hide": [
"destroy_vm"
]
}destroy_vm disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Destroy a specific VM. Args: vm_id: ID of the VM to destroy Returns: Destruction result. It is categorised as a Destructive tool in the Ludus FastMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for destroy_vm: 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 Ludus FastMCP. Nothing to install.
destroy_vm 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 destroy_vm 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 destroy_vm. 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.
destroy_vm is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.