force_destroy_domain
AI agents call force_destroy_domain to permanently remove resources in Libvirt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys/terminates a virtual machine domain without opportunity for recovery or graceful shutdown. Destruction of VMs is an unrecoverable operation with maximum blast radius—all workloads, data, and configurations on that domain are lost. This is the most severe category applicable. Critical severity reflects that an agent misusing this could destroy production infrastructure.
From the tool's definition Tool name 'force_destroy_domain' indicates forceful termination of a virtual machine domain. Sibling tools include 'delete_domain' and 'snapshot_delete', establishing a pattern where destroy/delete operations are present on this libvirt management server.
Attacks that exploit this kind of access
force_destroy_domain. It is categorised as a Destructive tool in the Libvirt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Libvirt MCP server in PolicyLayer and add a rule for force_destroy_domain: 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 Libvirt. Nothing to install.
force_destroy_domain 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 force_destroy_domain 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 force_destroy_domain. 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.
force_destroy_domain is provided by the Libvirt MCP server (rzippert/libvirt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →