dokploy_stop_application · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_stop_application does on Dokploy

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

This is Execute rather than Write because it triggers an external operational action (stopping a service) whose effects are immediate and depend on which application is targeted. While not destructive (the application data persists and can be restarted), it causes a service interruption and is more impactful than data modification.

From the tool's definition The tool "stops a running application" - this triggers an operational state change on an external system (Dokploy-managed infrastructure). Stopping an application is a control plane action that immediately affects running services.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_stop_application Rate-limited

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

FAQ

Questions about dokploy_stop_application

What does the dokploy_stop_application tool do? +

Stop a running application. It is categorised as a Execute tool in the Dokploy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dokploy_stop_application? +

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

What risk level is dokploy_stop_application? +

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

Can I rate-limit dokploy_stop_application? +

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

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

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