cloud_delete_server

Delete a Hetzner Cloud server. Deleting is free and stops billing, but it destroys the server, so it requires confirm true. Auto-created primary IPs are released by Hetzner shortly after.

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

What cloud_delete_server does on Hetzner

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

Why cloud_delete_server needs a policy

This tool permanently and irreversibly deletes a cloud server, which is the textbook definition of a Destructive action. The blast radius is critical because: (1) the deletion is permanent and cannot be undone, (2) any data stored on the server is lost, (3) services running on the server are immediately halted, and (4) the requirement for explicit confirmation (confirm true) indicates the developers recognized the…

From the tool's definition Tool name contains 'delete' and description explicitly states 'destroys the server' and 'it destroys the server, so it requires confirm true'. The action is irreversible—once deleted, the server and its data are permanently destroyed.

Questions about cloud_delete_server

What does the cloud_delete_server tool do? +

Delete a Hetzner Cloud server. Deleting is free and stops billing, but it destroys the server, so it requires confirm true. Auto-created primary IPs are released by Hetzner shortly after. It is categorised as a Destructive tool in the Hetzner 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 cloud_delete_server? +

Register the Hetzner MCP server in PolicyLayer and add a rule for cloud_delete_server: 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. Nothing to install.

What risk level is cloud_delete_server? +

cloud_delete_server 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 cloud_delete_server? +

Yes. Add a rate_limit block to the cloud_delete_server 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 cloud_delete_server completely? +

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

cloud_delete_server is provided by the Hetzner MCP server (mjmirza/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.