Update a Storage Box (rename, change labels, or toggle auto-delete).
AI agents use hetzner_update_storage_box 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.
This tool modifies storage box properties (name, labels, auto-delete setting) but does not delete data irreversibly or execute arbitrary code. These changes are reversible: names and labels can be changed again, and auto-delete can be toggled back on or off. It falls squarely in the Write category.
From the tool's definition Tool description states 'Update a Storage Box (rename, change labels, or toggle auto-delete)' — all reversible modifications to metadata and settings.
Attacks that exploit this kind of access
Update a Storage Box (rename, change labels, or toggle auto-delete). 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_update_storage_box: 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_update_storage_box 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_update_storage_box 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_update_storage_box. 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_update_storage_box 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 →