recover_snapshot

Recover from snapshot

SERVER1Panel MCP Server SOURCEeaveluo/1panel-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eaveluo-1panel-mcp/recover-snapshot.md

WHAT IT DOES

What recover_snapshot does on 1Panel MCP Server

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

RISK

Why recover_snapshot is rated Critical

Recovering from a snapshot overwrites the current system state with the snapshot's contents. This is an irreversible operation — any data, configurations, or changes made after the snapshot was taken will be permanently lost. Given this is a server infrastructure management tool affecting Docker containers, databases, websites, and system configurations, the blast radius of misuse is critical.

From the tool's definition recover_snapshot - 'Recover from snapshot' implies overwriting current system state with a previous snapshot, which irreversibly overwrites existing data and configurations

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs recover_snapshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recover_snapshot, this is the rule to start with:

recover_snapshot Hidden

recover_snapshot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every recover_snapshot call is checked against it from then on.

FAQ

Questions about recover_snapshot

What does the recover_snapshot tool do? +

Recover from snapshot. It is categorised as a Destructive tool in the 1Panel 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 recover_snapshot? +

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

What risk level is recover_snapshot? +

recover_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 recover_snapshot? +

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

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

recover_snapshot is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 1Panel MCP Server, and thousands of servers like it.

This server

All 286 1Panel MCP Server tools → Critical-risk tools on this server →

Across the catalogue

delete_snapshot on Why Did You Render → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →