Create a new volume in the VPSA storage array
AI agents use vpsa_create_volume to create or update resources in Zadara Storage MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zadara Storage MCP Server environment.
This tool creates new volumes in a storage array, which is a reversible write operation that allocates resources and modifies the storage system state. It is not destructive (volumes can be deleted), not financial, and not an execute-arbitrary-code operation.
From the tool's definition Tool name 'vpsa_create_volume' and description 'Create a new volume in the VPSA storage array' explicitly indicate data structure creation that modifies storage configuration.
Attacks that exploit this kind of access
Create a new volume in the VPSA storage array. It is categorised as a Write tool in the Zadara Storage MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zadara Storage MCP Server MCP server in PolicyLayer and add a rule for vpsa_create_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_create_volume 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 vpsa_create_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_create_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_create_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 →