plesk_restart_service · Plesk MCP Server MCP: Risk & Policy

WHAT IT DOES

What plesk_restart_service does on Plesk MCP Server

AI agents invoke plesk_restart_service to trigger actions in Plesk 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 plesk_restart_service needs a policy

Restarting system services is an Execute category action because it runs/triggers external operations whose consequences depend on the arguments supplied. While not destructive (services restart cleanly), it immediately impacts availability and system state.

From the tool's definition Tool name explicitly states 'restart_service' and description confirms it 'Restarts a specific system service (apache, nginx, mysql)' — this triggers external system operations with effects that depend on which service argument is provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plesk_restart_service Rate-limited

plesk_restart_service 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": {
    "plesk_restart_service": {
      "limits": [
        {
          "counter": "plesk_restart_service_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 Plesk MCP Server, so you can run agents against it safely.

FAQ

Questions about plesk_restart_service

What does the plesk_restart_service tool do? +

Restarts a specific system service (apache, nginx, mysql). It is categorised as a Execute tool in the Plesk 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 plesk_restart_service? +

Register the Plesk MCP Server MCP server in PolicyLayer and add a rule for plesk_restart_service: 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 Plesk MCP Server. Nothing to install.

What risk level is plesk_restart_service? +

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

Can I rate-limit plesk_restart_service? +

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

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

plesk_restart_service is provided by the Plesk MCP Server MCP server (klan1/plesk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.