drone_stop_build · Drone CI MCP Server MCP: Risk & Policy

WHAT IT DOES

What drone_stop_build does on Drone CI MCP Server

AI agents invoke drone_stop_build to trigger actions in Drone CI 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 drone_stop_build needs a policy

The tool executes an external operation that terminates a running CI/CD pipeline. While not destructive (reversible by restarting), it is not a simple read/write of persistent data — it triggers a command with external side effects.

From the tool's definition Tool description states "Stop one running build in Drone" — this triggers an external operation (stopping a CI/CD pipeline build) whose effects are immediate and depend on which build argument is provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drone_stop_build Rate-limited

drone_stop_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": {
    "drone_stop_build": {
      "limits": [
        {
          "counter": "drone_stop_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 Drone CI MCP Server, so you can run agents against it safely.

FAQ

Questions about drone_stop_build

What does the drone_stop_build tool do? +

Stop one running build in Drone. It is categorised as a Execute tool in the Drone CI 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 drone_stop_build? +

Register the Drone CI MCP Server MCP server in PolicyLayer and add a rule for drone_stop_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 Drone CI MCP Server. Nothing to install.

What risk level is drone_stop_build? +

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

Can I rate-limit drone_stop_build? +

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

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

drone_stop_build is provided by the Drone CI MCP Server MCP server (leuzeus/mcp-drone-ci). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.