stop_application

Stop a running application.

SERVERCoolify SOURCEcoolify-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/stop-application.md

WHAT IT DOES

What stop_application does on Coolify

AI agents invoke stop_application 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.

RISK

Why stop_application is rated High

This tool executes an operational command against infrastructure (stopping an application). While not destructive (the application can be restarted), it materially affects system state and availability. It belongs in Execute rather than Write because it triggers an external operation (a stop command) rather than modifying stored data reversibly.

From the tool's definition Tool name 'stop_application' and description 'Stop a running application' indicate an action that triggers external operations (stopping a running service/container) whose effects depend on which application is targeted.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_application 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 stop_application, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every stop_application call is checked against it from then on.

FAQ

Questions about stop_application

What does the stop_application tool do? +

Stop a running application. 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_application? +

Register the Coolify 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. 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 (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →