hetzner_reboot_server · Hetzner MCP Server MCP

WHAT IT DOES

What hetzner_reboot_server does on Hetzner MCP Server

AI agents invoke hetzner_reboot_server to trigger actions in Hetzner MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why hetzner_reboot_server needs a policy

A hard reboot forcibly resets a running server, interrupting all running processes and services. This is an external operation with significant operational impact (downtime, potential data corruption for running workloads), classifying it as Execute. It is not Destructive in the sense of permanent data loss, but misuse by an AI agent could cause high-severity service disruption.

From the tool's definition Reboot a server (hard reset). This is like pressing the reset button.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hetzner_reboot_server Rate-limited

hetzner_reboot_server stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hetzner_reboot_server": {
      "limits": [
        {
          "counter": "hetzner_reboot_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hetzner MCP Server, so you can run agents against it safely.

FAQ

Questions about hetzner_reboot_server

What does the hetzner_reboot_server tool do? +

Reboot a server (hard reset). This is like pressing the reset button. For a graceful reboot, SSH into the server and run. It is categorised as a Execute tool in the Hetzner MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hetzner_reboot_server? +

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

What risk level is hetzner_reboot_server? +

hetzner_reboot_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hetzner_reboot_server? +

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

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

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