Perform bulk operations on multiple VMs. Args: operation: Operation to perform (power_on, power_off, snapshot, delete) vm_names: Optional list of VM names (defaults to all VMs) parameters: Optional operation-specific parameters user_id: Optional user ID (admin only) Returns: Bulk operation results
AI agents call bulk_vm_operations 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.
Although this tool includes reversible operations (power_on, power_off, snapshot), the presence of 'delete' as an available operation makes this Destructive category. Deletion of VMs is irreversible and cannot be undone. The bulk nature amplifies risk—a single misconfigured call could destroy many VMs simultaneously. This represents the highest severity threat as it causes permanent loss of infrastructure and data.
From the tool's definition Tool accepts 'delete' as an operation parameter: 'operation: Operation to perform (power_on, power_off, snapshot, delete)'.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access bulk_vm_operations 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 bulk_vm_operations:
{
"version": "1",
"default": "deny",
"hide": [
"bulk_vm_operations"
]
}bulk_vm_operations 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.
Perform bulk operations on multiple VMs. Args: operation: Operation to perform (power_on, power_off, snapshot, delete) vm_names: Optional list of VM names (defaults to all VMs) parameters: Optional operation-specific parameters user_id: Optional user ID (admin only) Returns: Bulk operation results. 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 bulk_vm_operations: 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.
bulk_vm_operations 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 bulk_vm_operations 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 bulk_vm_operations. 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.
bulk_vm_operations 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.