dokploy_kill_build · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_kill_build does on Dokploy

AI agents invoke dokploy_kill_build 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_kill_build needs a policy

This tool executes a command to forcefully terminate an application's build process. While not destructive (does not delete data irreversibly) or financial, it is an Execute action because it triggers external operations whose effects depend on context (which build, application state, potential side effects from abrupt termination).

From the tool's definition Tool name 'dokploy_kill_build' and description 'Kill a stuck or hung build for an application' indicate termination of an ongoing external operation (a build process). The action 'kill' triggers an immediate interruption of a running process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_kill_build Rate-limited

dokploy_kill_build 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_kill_build": {
      "limits": [
        {
          "counter": "dokploy_kill_build_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_kill_build

What does the dokploy_kill_build tool do? +

Kill a stuck or hung build for an 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_kill_build? +

Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_kill_build: 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_kill_build? +

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

Can I rate-limit dokploy_kill_build? +

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

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

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