AI agents use create_volume to create or update resources in Hcloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hcloud environment.
This tool creates a new cloud storage volume, which is a reversible action—volumes can be deleted or modified after creation. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because misconfigured volumes could consume resources or expose sensitive data if not properly secured, but the action itself is not inherently destructive or dangerous.
From the tool's definition Tool name 'create_volume' and description 'Create a new volume' indicate the tool creates a new resource (volume) in the Hetzner Cloud infrastructure.
Attacks that exploit this kind of access
Create a new volume. It is categorised as a Write tool in the Hcloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hcloud 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 Hcloud. 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 Hcloud MCP server (xodus-co/hcloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_volume is one line of Hcloud's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →