stop_application · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_application does on Coolify MCP Server

AI agents invoke stop_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 stop_application needs a policy

Stopping an application is an Execute action—it triggers external operational effects (application halt) whose consequences depend on which application is targeted and when the action occurs. It is not Destructive because the application is not deleted and can be restarted. It is not Write because it does not create or modify data reversibly in the traditional sense; it changes operational state.

From the tool's definition Tool performs stop_application action that halts a running application, which is an operational change with immediate effects on system state and availability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_application Rate-limited

stop_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": {
    "stop_application": {
      "limits": [
        {
          "counter": "stop_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 stop_application

What does the stop_application tool do? +

Stop 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 stop_application? +

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

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

Can I rate-limit stop_application? +

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

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

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