stop_all_apps · Coolify MCP: Risk & Policy

WHAT IT DOES

What stop_all_apps does on Coolify

AI agents invoke stop_all_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 stop_all_apps needs a policy

This tool triggers external operations (stopping application processes) whose effects depend on which apps are running. While it doesn't delete data, it terminates service availability across an entire infrastructure, making it Execute rather than Destructive. The 'all' scope and EMERGENCY designation warrant high severity due to blast radius affecting all applications simultaneously.

From the tool's definition Tool name 'stop_all_apps' explicitly states it stops all running applications; description reinforces severity with 'EMERGENCY' label. The action is an irreversible operational change affecting all applications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_all_apps Rate-limited

stop_all_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": {
    "stop_all_apps": {
      "limits": [
        {
          "counter": "stop_all_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 stop_all_apps

What does the stop_all_apps tool do? +

EMERGENCY: Stop all running apps. 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 stop_all_apps? +

Register the Coolify MCP server in PolicyLayer and add a rule for stop_all_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 stop_all_apps? +

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

Can I rate-limit stop_all_apps? +

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

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

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