restart_application · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_application does on Coolify MCP Server

AI agents invoke restart_application 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_application needs a policy

This tool executes an external operation (restarting a service/application) rather than merely reading or writing data. It has immediate side effects on running infrastructure. While not destructive (the application can be restarted again) and not financial, it is Execute-category because it triggers an operational action.

From the tool's definition Tool name 'restart_application' and description 'Restart an application' directly trigger an external operation that restarts a running application instance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_application Rate-limited

restart_application 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_application": {
      "limits": [
        {
          "counter": "restart_application_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_application

What does the restart_application tool do? +

Restart an application. 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_application? +

Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for restart_application: 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_application? +

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

Can I rate-limit restart_application? +

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

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

restart_application 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.