application-stop · Dokploy MCP Server MCP: Risk & Policy

WHAT IT DOES

What application-stop does on Dokploy MCP Server

AI agents invoke application-stop to trigger actions in Dokploy 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 application-stop needs a policy

This tool executes an action that changes the state of a deployed application—stopping it is an operational trigger with real-world consequences (service downtime, user impact). While not destructive (the application can be restarted), it is not merely a read or write operation; it actively executes a command against infrastructure.

From the tool's definition Tool name 'application-stop' and description 'Stops an application in Dokploy' indicate this tool triggers an external operation (stopping a running application) whose effects depend on which application is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

application-stop Rate-limited

application-stop 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": {
    "application-stop": {
      "limits": [
        {
          "counter": "application-stop_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 Dokploy MCP Server, so you can run agents against it safely.

FAQ

Questions about application-stop

What does the application-stop tool do? +

Stops an application in Dokploy. It is categorised as a Execute tool in the Dokploy 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 application-stop? +

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

What risk level is application-stop? +

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

Can I rate-limit application-stop? +

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

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

application-stop is provided by the Dokploy MCP Server MCP server (limehawk/dokploy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.