restart_project_apps · Coolify MCP: Risk & Policy

WHAT IT DOES

What restart_project_apps does on Coolify

AI agents invoke restart_project_apps 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 IT NEEDS A POLICY

Why restart_project_apps needs a policy

Restarting applications is an Execute operation because it runs an external operational command with side effects. The severity is high because restarting production apps can cause service disruption, data loss if apps have in-flight transactions, or cascading failures. Confidence is high (0.9) because the intent is explicit, though the actual impact depends on the deployment context and which apps are affected.

From the tool's definition Tool performs 'Restart all apps in project' — an action that triggers external operations (application restart) whose effects depend on which project is targeted. This is an operational execution, not a data retrieval or modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_project_apps Rate-limited

restart_project_apps 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_project_apps": {
      "limits": [
        {
          "counter": "restart_project_apps_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, so you can run agents against it safely.

FAQ

Questions about restart_project_apps

What does the restart_project_apps tool do? +

Restart all apps in project. It is categorised as a Execute tool in the Coolify 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_project_apps? +

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

What risk level is restart_project_apps? +

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

Can I rate-limit restart_project_apps? +

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

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

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