restart_service

What restart_service does on Coolify

AI agents invoke restart_service to trigger actions in Coolify. 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 restart_service is rated High

The tool triggers a restart action on a service, which is an operational command with immediate effects on system state. This falls under Execute rather than Write because it runs/triggers an external operation whose effects depend on which service is targeted. While not destructive or financial, restarting a service can cause downtime and service interruption, warranting high severity.

From the tool's definition Tool name 'restart_service' with description 'Restart a service' indicates execution of a service restart operation, which is an external operation with real-world effects on infrastructure.

The rule that runs restart_service safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restart_service, this is the rule to start with:

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

Questions about restart_service