restart_service · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_service does on Coolify MCP Server

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

Restarting a service is an Execute category action because it runs/triggers an operation on external infrastructure whose effects depend on which service is targeted. While not destructive (reversible), it causes immediate operational impact—downtime, service interruption, and potential data loss if services are not properly shut down.

From the tool's definition Tool name 'restart_service' and description 'Restart a service' indicates triggering an external operation that restarts infrastructure services. The context shows this is part of Coolify PaaS management with direct control over deployed systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_service Rate-limited

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

FAQ

Questions about restart_service

What does the restart_service tool do? +

Restart a service. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter. It is categorised as a Execute tool in the Coolify 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 restart_service? +

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

What risk level is restart_service? +

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

Can I rate-limit restart_service? +

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

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

restart_service is provided by the Coolify MCP Server MCP server (kof70/coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.