bitbucket_trigger_pipeline

What bitbucket_trigger_pipeline does on Sage MCP

AI agents invoke bitbucket_trigger_pipeline to trigger actions in Sage MCP. 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 bitbucket_trigger_pipeline is rated High

This tool executes a pipeline — an external operation that runs code and can have side effects ranging from building/testing to deploying software. While not inherently destructive by itself, the consequences depend on what the pipeline contains. It is Execute rather than Destructive because the tool itself does not directly delete or overwrite data; it merely triggers automation.

From the tool's definition Tool name contains 'trigger' and description states 'Trigger a new pipeline run for a branch or commit' — this initiates external operations (CI/CD pipeline execution) whose effects depend on the specified branch/commit arguments and cannot be easily reversed…

The rule that runs bitbucket_trigger_pipeline safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitbucket_trigger_pipeline, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitbucket_trigger_pipeline": {
      "limits": [
        {
          "counter": "bitbucket_trigger_pipeline_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about bitbucket_trigger_pipeline