batch_remove_snapshots
Remove snapshots from multiple VMs in parallel.
This record as markdown: /tools/tjnull-ludus-fastmcp/batch-remove-snapshots.md
What batch_remove_snapshots does on Ludus FastMCP
AI agents call batch_remove_snapshots 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.
Why batch_remove_snapshots is rated Critical
Snapshot removal is a destructive operation that cannot be undone. In a cyber range environment, snapshots are critical recovery points; removing them eliminates the ability to revert VMs to previous states, which could disrupt testing scenarios, cause data loss, or compromise research integrity. The parallel execution across multiple VMs amplifies the blast radius.
From the tool's definition Tool name explicitly states 'remove' snapshots; description confirms deletion action ('Remove snapshots from multiple VMs in parallel'). Snapshot removal is irreversible—once deleted, snapshots cannot be recovered.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_remove_snapshots safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_remove_snapshots, this is the rule to start with:
batch_remove_snapshots 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 Ludus FastMCP, apply this rule, and every batch_remove_snapshots call is checked against it from then on.
Questions about batch_remove_snapshots
Remove snapshots from multiple VMs in parallel. 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 batch_remove_snapshots: 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.
batch_remove_snapshots 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 batch_remove_snapshots 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 batch_remove_snapshots. 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.
batch_remove_snapshots 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.
More on Ludus Fast, and thousands of servers like it.
Across the catalogue