storage_volumes_prune_backups
Run storage-volumes.prune-backups through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/storage-volumes-prune-backups.md
What storage_volumes_prune_backups does on Appaloft
AI agents call storage_volumes_prune_backups 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 |
|---|---|---|---|
backupId | string | Yes |
Parameters from the server's own tool schema.
Why storage_volumes_prune_backups is rated Critical
Pruning backups is a destructive operation — it permanently removes backup snapshots for storage volumes. Once backups are pruned, they cannot be recovered, making this irreversible. The blast radius is high because losing backups eliminates the ability to restore data after incidents.
From the tool's definition 'prune-backups' in the tool name indicates irreversible deletion of backup data; 'prune' consistently means removing/deleting entries that cannot be recovered
Attacks that exploit this kind of access
The rule that runs storage_volumes_prune_backups 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_prune_backups, this is the rule to start with:
storage_volumes_prune_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 Appaloft, apply this rule, and every storage_volumes_prune_backups call is checked against it from then on.
Questions about storage_volumes_prune_backups
Run storage-volumes.prune-backups 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_prune_backups accepts 1 parameter: backupId. Required: backupId. 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_prune_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 Appaloft. Nothing to install.
storage_volumes_prune_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 storage_volumes_prune_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 storage_volumes_prune_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.
storage_volumes_prune_backups 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