storage_volumes_delete
Run storage-volumes.delete through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/storage-volumes-delete.md
What storage_volumes_delete does on Appaloft
AI agents call storage_volumes_delete to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
storageVolumeId | string | Yes |
Parameters from the server's own tool schema.
Why storage_volumes_delete is rated Critical
This tool performs a destructive operation that removes storage volumes, which cannot be undone. The deletion of storage infrastructure is a high-blast-radius action that could cause data loss and service disruption if triggered inappropriately by an AI agent.
From the tool's definition Tool name 'storage_volumes_delete' combined with description stating it 'delete[s]' through the application operation catalog indicates irreversible deletion of storage volumes.
Attacks that exploit this kind of access
The rule that runs storage_volumes_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_volumes_delete, this is the rule to start with:
storage_volumes_delete 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 Appaloft, apply this rule, and every storage_volumes_delete call is checked against it from then on.
Questions about storage_volumes_delete
Run storage-volumes.delete through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
storage_volumes_delete accepts 1 parameter: storageVolumeId. Required: storageVolumeId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for storage_volumes_delete: 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 Appaloft. Nothing to install.
storage_volumes_delete 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 storage_volumes_delete 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 storage_volumes_delete. 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.
storage_volumes_delete is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue