storage_volumes_create_backup
Run storage-volumes.create-backup through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/storage-volumes-create-backup.md
What storage_volumes_create_backup does on Appaloft
AI agents use storage_volumes_create_backup to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
planRequest | object | Yes | |
storageVolumeId | string | Yes |
Parameters from the server's own tool schema.
Why storage_volumes_create_backup is rated Medium
This tool creates (writes) a backup of storage volumes. While backups are generally protective in intent, the operation itself is a write action that creates new data structures and consumes resources. It is reversible (backups can be deleted), so it does not qualify as Destructive.
From the tool's definition Tool name 'storage_volumes_create_backup' indicates creation of a backup, which is a write operation that creates new data. Description confirms it 'Run[s] storage-volumes.create-backup through the Appaloft application operation catalog.'
Risk signalsHigh parameter count (22 properties)
Attacks that exploit this kind of access
The rule that runs storage_volumes_create_backup 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_create_backup, this is the rule to start with:
storage_volumes_create_backup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every storage_volumes_create_backup call is checked against it from then on.
Questions about storage_volumes_create_backup
Run storage-volumes.create-backup through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
storage_volumes_create_backup accepts 2 parameters: planRequest, storageVolumeId. Required: planRequest, 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_create_backup: 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_create_backup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the storage_volumes_create_backup 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_create_backup. 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_create_backup 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.
This server
Across the catalogue