power_on_server · Hcloud MCP: Risk & Policy

WHAT IT DOES

What power_on_server does on Hcloud

AI agents invoke power_on_server to trigger actions in Hcloud. 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 power_on_server needs a policy

Powering on a server triggers an external infrastructure operation. It is not a simple data read or write, but an execution of a state change on a live cloud resource. It is reversible (the server can be powered off), so it is not Destructive, but it does execute an action with real-world side effects such as incurring compute costs and starting services.

From the tool's definition 'Power on a server' — triggers an external operation that starts a cloud server instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

power_on_server Rate-limited

power_on_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": {
    "power_on_server": {
      "limits": [
        {
          "counter": "power_on_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 Hcloud, so you can run agents against it safely.

FAQ

Questions about power_on_server

What does the power_on_server tool do? +

Power on a server. It is categorised as a Execute tool in the Hcloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on power_on_server? +

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

What risk level is power_on_server? +

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

Can I rate-limit power_on_server? +

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

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

power_on_server is provided by the Hcloud MCP server (xodus-co/hcloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.