Create a new block storage volume.
AI agents use create_volume to create or update resources in Verda Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Verda Cloud MCP Server environment.
This tool creates cloud infrastructure resources (block storage volumes), which is a reversible write operation. The severity is medium because creating volumes consumes cloud resources and may incur costs, but the action is not destructive and can be reversed by deleting the volume. This represents a write-class operation that modifies the cloud infrastructure state.
From the tool's definition Tool name 'create_volume' and description 'Create a new block storage volume' indicate creation of new persistent storage resources.
Attacks that exploit this kind of access
Create a new block storage volume. It is categorised as a Write tool in the Verda Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Verda Cloud MCP Server MCP server in PolicyLayer and add a rule for 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 Verda Cloud MCP Server. Nothing to install.
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 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 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.
create_volume is provided by the Verda Cloud MCP Server MCP server (sniper35/verda-cloud-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 →