Hetzner

3 tools. 2 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

2 can modify or destroy data
1 read-only
3 tools total

Community server · catalogue entry verified 02/07/2026

How to control Hetzner ↓

What Hetzner exposes to your agents

Read (1) Write / Execute (0) Destructive / Financial (2)
Critical Risk

The most dangerous Hetzner tools

2 of Hetzner's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Hetzner

PolicyLayer is an MCP gateway — it sits between your AI agents and Hetzner, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "cloud_create_server": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
{
  "cloud_delete_server": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations
{
  "contribute_or_report": {
    "limits": [
      {
        "counter": "contribute_or_report_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Hetzner — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON HETZNER →

Instant setup, no code required.

All 3 Hetzner tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Hetzner

Can an AI agent move money through the Hetzner MCP server? +

Yes. The Hetzner server exposes 1 financial tools including cloud_create_server. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Hetzner MCP server? +

Yes. The Hetzner server exposes 1 destructive tools including cloud_delete_server. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Hetzner MCP server expose? +

3 tools across 2 categories: Destructive, Write. 1 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Hetzner? +

Register the Hetzner MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Hetzner tool call.

Deterministic rules across all 3 Hetzner tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

3 Hetzner tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.