delete_container_snapshot

Delete a container snapshot.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-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/gethosthewalrus-proxmox-mcp/delete-container-snapshot.md

What delete_container_snapshot does on Proxmox MCP Server

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

Why delete_container_snapshot is rated Critical

Snapshot deletion is destructive because it permanently removes a point-in-time backup of container state. Once deleted, the snapshot cannot be recovered, and any data or configuration state captured in that snapshot is lost.

From the tool's definition Tool name is 'delete_container_snapshot' which explicitly performs a delete operation on snapshot data. Description confirms 'Delete a container snapshot,' an irreversible action that cannot be undone.

Questions about delete_container_snapshot

What does the delete_container_snapshot tool do? +

Delete a container snapshot. It is categorised as a Destructive tool in the Proxmox 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 delete_container_snapshot? +

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

What risk level is delete_container_snapshot? +

delete_container_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 delete_container_snapshot? +

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

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

delete_container_snapshot is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.