bb_trigger_pipeline · Bitbucket Cloud MCP Server MCP

WHAT IT DOES

What bb_trigger_pipeline does on Bitbucket Cloud MCP Server

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

This tool initiates external operations (CI/CD pipelines) whose effects are determined by the arguments provided and the pipeline definitions in the repository. Pipeline runs can execute arbitrary build scripts, deploy code, run tests, or perform other side effects.

From the tool's definition Tool name and description: "Trigger a new pipeline run in a Bitbucket repository" — the word "trigger" combined with "pipeline run" indicates execution of automated workflows whose behavior depends on repository content, branch selection, and pipeline…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bb_trigger_pipeline Rate-limited

bb_trigger_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": {
    "bb_trigger_pipeline": {
      "limits": [
        {
          "counter": "bb_trigger_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 Cloud MCP Server, so you can run agents against it safely.

FAQ

Questions about bb_trigger_pipeline

What does the bb_trigger_pipeline tool do? +

Trigger a new pipeline run in a Bitbucket repository. It is categorised as a Execute tool in the Bitbucket Cloud 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 bb_trigger_pipeline? +

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

What risk level is bb_trigger_pipeline? +

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

Can I rate-limit bb_trigger_pipeline? +

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

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

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