storage_volumes_rename
Run storage-volumes.rename through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/storage-volumes-rename.md
What storage_volumes_rename does on Appaloft
AI agents use storage_volumes_rename 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 |
|---|---|---|---|
name | string | Yes | |
storageVolumeId | string | Yes |
Parameters from the server's own tool schema.
Why storage_volumes_rename is rated Medium
Renaming storage volumes is a write operation that modifies infrastructure configuration reversibly. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The medium severity reflects that renaming volumes could cause operational confusion or service disruption if misapplied, but the change is reversible.
From the tool's definition Tool name 'storage_volumes_rename' and description states it runs 'storage-volumes.rename' operation. The rename operation modifies metadata of storage volumes (their names) reversibly without deleting data.
Attacks that exploit this kind of access
The rule that runs storage_volumes_rename 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_rename, this is the rule to start with:
storage_volumes_rename 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_rename call is checked against it from then on.
Questions about storage_volumes_rename
Run storage-volumes.rename 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_rename accepts 2 parameters: name, storageVolumeId. Required: name, 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_rename: 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_rename 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_rename 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_rename. 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_rename 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