AI agents call get_pipeline_config 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 configuration data about CI/CD pipeline settings. It performs a read-only query to check pipeline enablement status and configuration. There is no modification, execution, deletion, or financial impact. The blast radius if misused is minimal—at most, an attacker gains visibility into pipeline configuration, which could inform further attacks but causes no direct harm.
From the tool's definition Tool name 'get_pipeline_config' and description 'Get pipeline configuration for a repository (check if pipelines are enabled)' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get pipeline configuration for a repository (check if pipelines are enabled). 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_pipeline_config: 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_pipeline_config 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_pipeline_config 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_pipeline_config. 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_pipeline_config is provided by the Bitbucket MCP server (javimaligno/mcp-server-bitbucket). 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 →