Critical Risk →

RestoreSnapshot

Restore a virtual machine to a previous snapshot.

How to control RestoreSnapshot ↓

What RestoreSnapshot does on Virtualization

AI agents call RestoreSnapshot to permanently remove resources in Virtualization — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why RestoreSnapshot needs a policy

Restoring a VM to a previous snapshot irreversibly discards all changes made to the VM after that snapshot was taken, including data, configurations, and state. This is a destructive, non-reversible operation since the post-snapshot state is lost permanently.

From the tool's definition Restore a virtual machine to a previous snapshot

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

How to control RestoreSnapshot

PolicyLayer is an MCP gateway — it sits between your AI agents and Virtualization, and nothing reaches the server without passing your rules. This is the rule we recommend for RestoreSnapshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "RestoreSnapshot"
  ]
}

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

  1. Create a free account and register Virtualization — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about RestoreSnapshot

What does the RestoreSnapshot tool do? +

Restore a virtual machine to a previous snapshot. It is categorised as a Destructive tool in the Virtualization 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 RestoreSnapshot? +

Register the Virtualization MCP server in PolicyLayer and add a rule for RestoreSnapshot: 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 Virtualization. Nothing to install.

What risk level is RestoreSnapshot? +

RestoreSnapshot 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 RestoreSnapshot? +

Yes. Add a rate_limit block to the RestoreSnapshot 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 RestoreSnapshot completely? +

Set action: deny in the PolicyLayer policy for RestoreSnapshot. 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 RestoreSnapshot? +

RestoreSnapshot is provided by the Virtualization MCP server (sandraschi/virtualization-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Virtualization tool call.

Start from Virtualization, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

56 Virtualization tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.