hetzner_delete_storage_box

Delete a Storage Box permanently. ⚠️ DESTRUCTIVE: All data, snapshots, and subaccounts will be permanently deleted. This action cannot be undone.

Server Hetzner MCP Server jurislm/hetzner-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What hetzner_delete_storage_box does on Hetzner MCP Server

AI agents call hetzner_delete_storage_box to permanently remove resources in Hetzner MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why hetzner_delete_storage_box needs a policy

This tool irreversibly deletes storage infrastructure and all associated data without recovery options. The blast radius is maximal: loss of customer data, snapshots, and subaccounts. Permanent deletion of cloud resources qualifies as Destructive (most severe category), warranting critical severity.

From the tool's definition Tool description explicitly states: 'Delete a Storage Box permanently' with warning 'All data, snapshots, and subaccounts will be permanently deleted. This action cannot be undone.'

Risk signalsBulk/mass operation — affects multiple targets

Questions about hetzner_delete_storage_box

What does the hetzner_delete_storage_box tool do? +

Delete a Storage Box permanently. ⚠️ DESTRUCTIVE: All data, snapshots, and subaccounts will be permanently deleted. This action cannot be undone. It is categorised as a Destructive tool in the Hetzner MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on hetzner_delete_storage_box? +

Register the Hetzner MCP Server MCP server in PolicyLayer and add a rule for hetzner_delete_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.

What risk level is hetzner_delete_storage_box? +

hetzner_delete_storage_box is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hetzner_delete_storage_box? +

Yes. Add a rate_limit block to the hetzner_delete_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.

How do I block hetzner_delete_storage_box completely? +

Set action: deny in the PolicyLayer policy for hetzner_delete_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.

What MCP server provides hetzner_delete_storage_box? +

hetzner_delete_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.