// MCP TOOL REFERENCE

batch_remove_snapshots

Remove snapshots from multiple VMs in parallel. Args: vm_names: List of VM names snapshot_name: Name of snapshot to remove user_id: Optional user ID (admin only) Returns: Results for each VM

ServerLudus FastMCP
CategoryDestructive

How to control batch_remove_snapshots ↓

WHAT BATCH_REMOVE_SNAPSHOTS ON LUDUS FASTMCP DOES

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.

THE RISK

Critical Risk

The tool permanently deletes snapshots from virtual machines without the ability to undo the operation. This is a destructive action that cannot be reversed once executed.

From the tool's definition Tool name 'batch_remove_snapshots' and description 'Remove snapshots from multiple VMs in parallel' indicates irreversible deletion of snapshot data.

Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation

Documented attack patterns abuse exactly the kind of access batch_remove_snapshots gives an agent:

HOW TO CONTROL BATCH_REMOVE_SNAPSHOTS

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 batch_remove_snapshots:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "batch_remove_snapshots"
  ]
}

batch_remove_snapshots disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Ludus FastMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Ludus FastMCP tools

Destructive abort_and_remove_range Abort any active deployment and then remove the range. This is a convenie Destructive bulk_vm_operations Perform bulk operations on multiple VMs. Args: operation: Operation t Destructive clear_range_access Clear all range access permissions. Args: user_id: Optional user ID ( Destructive delete_blueprint Delete a blueprint. Args: blueprint_id: ID of the blueprint to delete Destructive delete_group Delete a group. Args: group_name: Name of the group to delete Destructive delete_range Delete the entire range. Permanently removes the range and all associated VMs, sn Destructive delete_range_by_user delete_range_by_user Destructive delete_ranges_by_status delete_ranges_by_status

All 201 Ludus FastMCP tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Ludus FastMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the batch_remove_snapshots tool do? +

Remove snapshots from multiple VMs in parallel. Args: vm_names: List of VM names snapshot_name: Name of snapshot to remove user_id: Optional user ID (admin only) Returns: Results for each VM. 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.

How do I enforce a policy on batch_remove_snapshots? +

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.

What risk level is batch_remove_snapshots? +

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.

Can I rate-limit batch_remove_snapshots? +

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.

How do I block batch_remove_snapshots completely? +

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.

What MCP server provides batch_remove_snapshots? +

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.

Enforce policy on every Ludus FastMCP tool call.

Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN LUDUS FASTMCP →

Free to start. No card required.

201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

batch_remove_snapshots

// WHAT BATCH_REMOVE_SNAPSHOTS ON LUDUS FASTMCP DOES

// THE RISK

// HOW TO CONTROL BATCH_REMOVE_SNAPSHOTS

// EXPLORE