hetzner_delete_ssh_key

Delete an SSH key from the project. This does NOT affect existing servers that were created with this key. They will continue to work with the key.

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

What hetzner_delete_ssh_key does on Hetzner MCP Server

AI agents call hetzner_delete_ssh_key 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_ssh_key needs a policy

Deleting an SSH key is a destructive action that permanently removes authentication credentials from the Hetzner Cloud project. Although the tool clarifies that existing servers continue to function, the key itself is irreversibly removed, preventing future authentication with that key and blocking new server provisioning attempts that reference it. This meets the Destructive category criteria.

From the tool's definition The tool name includes 'delete' and the description explicitly states 'Delete an SSH key from the project.' This is an irreversible deletion operation that cannot be undone.

Questions about hetzner_delete_ssh_key

What does the hetzner_delete_ssh_key tool do? +

Delete an SSH key from the project. This does NOT affect existing servers that were created with this key. They will continue to work with the key. 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_ssh_key? +

Register the Hetzner MCP Server MCP server in PolicyLayer and add a rule for hetzner_delete_ssh_key: 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_ssh_key? +

hetzner_delete_ssh_key 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_ssh_key? +

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

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

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