prune_storage_backups
A destructive tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/prune-storage-backups.md
What prune_storage_backups does on Proxmox MCP Server
AI agents call prune_storage_backups 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 prune_storage_backups is rated Critical
'Prune' in the context of backups universally means deleting older or excess backup copies based on retention policies. This is an irreversible operation: once backup files are deleted from storage, they cannot be recovered (they are themselves the recovery mechanism). On a Proxmox VE server managing VMs and containers, destroying backups is a critical action.
From the tool's definition Tool name 'prune_storage_backups' — 'prune' implies irreversible deletion of backup files from storage.
Attacks that exploit this kind of access
The rule that runs prune_storage_backups safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prune_storage_backups, this is the rule to start with:
prune_storage_backups is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every prune_storage_backups call is checked against it from then on.
Questions about prune_storage_backups
prune_storage_backups is a destructive tool on the Proxmox MCP Server MCP server. 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.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for prune_storage_backups: 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.
prune_storage_backups is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the prune_storage_backups 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.
Set action: deny in the PolicyLayer policy for prune_storage_backups. 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.
prune_storage_backups 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.
Across the catalogue