Destroy a Ludus range, permanently removing all VMs and freeing resources. This action is irreversible and will delete all data. IMPORTANT LLM BEHAVIORAL PROMPTS: - SAFETY FIRST: Ludus operations can be destructive and time-consuming - VERIFY DESTRUCTIVE ACTIONS: Always confirm with user before d...
AI agents call destroy_range to permanently remove resources in LudusMCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly performs irreversible deletion of virtualized environments (VMs) and all associated data. The description uses absolute language: 'permanently removing', 'irreversible', and 'delete all data'.
From the tool's definition "Destroy a Ludus range, permanently removing all VMs and freeing resources. This action is irreversible and will delete all data."
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access destroy_range gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LudusMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for destroy_range:
{
"version": "1",
"default": "deny",
"hide": [
"destroy_range"
]
}destroy_range 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 Ludus range, permanently removing all VMs and freeing resources. This action is irreversible and will delete all data. IMPORTANT LLM BEHAVIORAL PROMPTS: - SAFETY FIRST: Ludus operations can be destructive and time-consuming - VERIFY DESTRUCTIVE ACTIONS: Always confirm with user before destroy/delete operations - CHECK EXISTING STATE: Use list_user_ranges or get_range_status before major operations - DESTRUCTION IS PERMANENT: Destroying ranges deletes all VMs and data irreversibly - ADMIN vs USER: Admin operations (--user flag) affect other users. It is categorised as a Destructive tool in the LudusMCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LudusMCP Server MCP server in PolicyLayer and add a rule for destroy_range: 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 LudusMCP Server. Nothing to install.
destroy_range 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_range 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_range. 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_range is provided by the LudusMCP Server MCP server (noctedefensor/ludusmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 LudusMCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 LudusMCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.