Get status and details for a specific pipeline run
AI agents call bitbucket_get_pipeline to retrieve information from ContextForge MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and status information about a pipeline run in Bitbucket. It performs a query-only operation (get) that does not create, modify, delete, or execute any pipelines or external operations. The blast radius of misuse is minimal: an agent could only read existing pipeline status data, which is typically non-sensitive operational metadata.
From the tool's definition Tool description states 'Get status and details for a specific pipeline run' — a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get status and details for a specific pipeline run. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for bitbucket_get_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 ContextForge MCP Gateway. Nothing to install.
bitbucket_get_pipeline 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 bitbucket_get_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_get_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_get_pipeline is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →