AI agents call get_pr_pipeline_status to retrieve information from Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries pipeline status data associated with a PR. It performs a read-only operation—fetching information about pipeline execution state and steps—without modifying any data, executing code, or triggering external operations. The action is purely informational and carries minimal risk.
From the tool's definition Tool name 'get_pr_pipeline_status' and description 'Get the status of pipelines triggered by this PR' indicate a retrieval operation that queries pipeline status information with no side effects.
Attacks that exploit this kind of access
Get the status of pipelines triggered by this PR (most recent first), with each step. It is categorised as a Read tool in the Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP server in PolicyLayer and add a rule for get_pr_pipeline_status: 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.
get_pr_pipeline_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pr_pipeline_status 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 get_pr_pipeline_status. 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.
get_pr_pipeline_status is provided by the Bitbucket MCP server (jacobpixleratgather/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →