Trigger a new pipeline run for a branch or commit
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.
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…
Documented attack patterns abuse exactly the kind of access bitbucket_trigger_pipeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bitbucket_trigger_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"bitbucket_trigger_pipeline": {
"limits": [
{
"counter": "bitbucket_trigger_pipeline_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}bitbucket_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.
Free to start. No card required.
Trigger a new pipeline run for a branch or commit. It is categorised as a Execute tool in the Sage MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sage MCP server in PolicyLayer and add a rule for bitbucket_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 Sage MCP. Nothing to install.
bitbucket_trigger_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bitbucket_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.
Set action: deny in the PolicyLayer policy for bitbucket_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.
bitbucket_trigger_pipeline is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.