delete_storage_volume
Delete a volume from storage.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/delete-storage-volume.md
What delete_storage_volume does on Proxmox MCP Server
AI agents call delete_storage_volume 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_storage_volume is rated Critical
Deleting a storage volume is a destructive operation that permanently removes data from the infrastructure and cannot be undone. While not directly financial, the loss of critical storage can have severe business impact. This falls squarely in the Destructive category due to its irreversible nature and high blast radius in a virtualization environment where storage volumes may contain critical VM or container data.
From the tool's definition Tool name is 'delete_storage_volume' and description states 'Delete a volume from storage.' The verb 'delete' combined with 'volume' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_storage_volume 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 delete_storage_volume, this is the rule to start with:
delete_storage_volume 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 delete_storage_volume call is checked against it from then on.
Questions about delete_storage_volume
Delete a volume from storage. 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 delete_storage_volume: 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.
delete_storage_volume 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 delete_storage_volume 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 delete_storage_volume. 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.
delete_storage_volume 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