Delete a volume from the VPSA storage array
AI agents call vpsa_delete_volume to permanently remove resources in Zadara Storage MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a volume from a storage array permanently removes the underlying data storage resource and any data it contains. This action cannot be undone and represents the most severe class of operation. Even if a snapshot exists elsewhere, the volume itself and any unprotected data are lost irretrievably.
From the tool's definition Tool name is 'vpsa_delete_volume' and description states 'Delete a volume from the VPSA storage array'. The verb 'delete' combined with 'volume' (a persistent storage resource) indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a volume from the VPSA storage array. It is categorised as a Destructive tool in the Zadara Storage MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zadara Storage MCP Server MCP server in PolicyLayer and add a rule for vpsa_delete_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 Zadara Storage MCP Server. Nothing to install.
vpsa_delete_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 vpsa_delete_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 vpsa_delete_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.
vpsa_delete_volume is provided by the Zadara Storage MCP Server MCP server (zadarastorage/zadara-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →