Delete a server permanently. ⚠️ This action is irreversible. All data on the server will be lost.
AI agents call hetzner_delete_server 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.
The tool permanently deletes a server and all associated data with no undo capability. This is a destructive operation with maximal blast radius—loss of complete infrastructure and data. It is irreversible by design, making it the most severe category.
From the tool's definition Delete a server permanently. All data on the server will be lost. ⚠️ This action is irreversible.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete a server permanently. ⚠️ This action is irreversible. All data on the server will be lost. 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.
Register the Hetzner MCP Server MCP server in PolicyLayer and add a rule for hetzner_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 MCP Server. Nothing to install.
hetzner_delete_server is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hetzner_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.
Set action: deny in the PolicyLayer policy for hetzner_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.
hetzner_delete_server 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 →