stop_pipeline · Bitbucket MCP: Risk & Policy

WHAT IT DOES

What stop_pipeline does on Bitbucket

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

Stopping a pipeline is an executable action that interrupts an active process in external CI/CD systems. While the operation is theoretically reversible (the pipeline can be restarted), it halts ongoing work and could disrupt deployments or builds. The blast radius is significant—an agent could maliciously stop critical production pipelines, causing service delays or failed releases.

From the tool's definition stop_pipeline stops a running pipeline, which is an external operation that triggers an immediate state change in CI/CD infrastructure. This is not a read-only query, nor is it a reversible data modification (write), nor is it destructive deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_pipeline Rate-limited

stop_pipeline 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_pipeline": {
      "limits": [
        {
          "counter": "stop_pipeline_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 Bitbucket, so you can run agents against it safely.

FAQ

Questions about stop_pipeline

What does the stop_pipeline tool do? +

Stop a running pipeline. It is categorised as a Execute tool in the Bitbucket 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_pipeline? +

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

What risk level is stop_pipeline? +

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

Can I rate-limit stop_pipeline? +

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

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

stop_pipeline is provided by the Bitbucket MCP server (javimaligno/mcp-server-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.