Attach a Cloud Volume to a server. The server must be in the same location as the volume. The volume must be in \
AI agents use hetzner_attach_volume to create or update resources in Hetzner MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hetzner MCP Server environment.
Attaching a volume to a server modifies the server's configuration and storage configuration reversibly. While this changes infrastructure state, it is not destructive (can be detached), not financial, and not code execution. It fits the Write category as a configuration modification.
From the tool's definition Tool description states 'Attach a Cloud Volume to a server' — this is a modification operation that creates a persistent attachment between resources.
Attacks that exploit this kind of access
Attach a Cloud Volume to a server. The server must be in the same location as the volume. The volume must be in \. It is categorised as a Write tool in the Hetzner MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hetzner MCP Server MCP server in PolicyLayer and add a rule for hetzner_attach_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 Hetzner MCP Server. Nothing to install.
hetzner_attach_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 hetzner_attach_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 hetzner_attach_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.
hetzner_attach_volume is provided by the Hetzner MCP Server MCP server (jurislm/hetzner-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 →