Critical Risk →

liara_restore_snapshot

Restore a VM from a snapshot

How to control liara_restore_snapshot ↓

What liara_restore_snapshot does on Liara MCP Server

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

Critical Risk

Why liara_restore_snapshot needs a policy

Restoring a VM from a snapshot is a destructive operation because it irreversibly overwrites the current state of the virtual machine with the snapshot state. Any data, configurations, or changes made after the snapshot was captured are permanently lost.

From the tool's definition 'Restore a VM from a snapshot' — restoring from a snapshot overwrites the current VM state irreversibly, destroying all data and changes made after the snapshot was taken.

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

How to control liara_restore_snapshot

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

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

liara_restore_snapshot 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 Liara MCP Server — 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 liara_restore_snapshot

What does the liara_restore_snapshot tool do? +

Restore a VM from a snapshot. It is categorised as a Destructive tool in the Liara MCP Server 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 liara_restore_snapshot? +

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

What risk level is liara_restore_snapshot? +

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

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

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

liara_restore_snapshot is provided by the Liara MCP Server MCP server (razavioo/liara-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Liara MCP Server tool call.

Start from Liara MCP Server, 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.

108 Liara MCP Server 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.