AI agents call list_prs 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 queries and retrieves pull request metadata from Bitbucket. It performs filtering and listing only, with no ability to modify, create, delete, or execute operations. The 'list' verb and read-only filtering parameters confirm it is a Read operation. Severity is low because exposure of PR metadata, while potentially sensitive, does not enable destructive or financial actions.
From the tool's definition Tool name is 'list_prs' and description states 'List pull requests in a Bitbucket repository. Filter by state, author UUID, or branch. Returns up to' — a query operation that retrieves data with no side effects.
Attacks that exploit this kind of access
List pull requests in a Bitbucket repository. Filter by state, author UUID, or branch. Returns up to. 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 list_prs: 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.
list_prs 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 list_prs 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 list_prs. 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.
list_prs 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 →