restart_server · OPanel MCP: Risk & Policy

WHAT IT DOES

What restart_server does on OPanel MCP

AI agents invoke restart_server to trigger actions in OPanel MCP. 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 restart_server needs a policy

This tool executes a significant external operation (server restart) that interrupts service and affects all connected users. While not directly destructive (data is saved first), it is an Execute-category action because it runs a complex, stateful operation whose exact effects depend on server context.

From the tool's definition Tool description states it will 'stop the Minecraft server, and restart the server again' — this triggers external operations (server shutdown and restart) whose effects depend on execution timing and server state, and cannot be precisely predicted without…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_server Rate-limited

restart_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": {
    "restart_server": {
      "limits": [
        {
          "counter": "restart_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 OPanel MCP, so you can run agents against it safely.

FAQ

Questions about restart_server

What does the restart_server tool do? +

Safely saving all states and stop the Minecraft server, and restart the server again after 10s. It is categorised as a Execute tool in the OPanel MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on restart_server? +

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

What risk level is restart_server? +

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

Can I rate-limit restart_server? +

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

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

restart_server is provided by the OPanel MCP server (opanel-mc/opanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.