List activity (comments, approvals, updates) on a pull request
AI agents call bb_list_pull_request_activity to retrieve information from Bitbucket Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves existing pull request activity data without creating, modifying, deleting, executing code, or affecting financial operations. The blast radius of misuse is minimal; an agent could only over-retrieve or spam read requests, which Bitbucket's rate limiting would mitigate.
From the tool's definition Tool name contains 'list' and description states it 'List activity (comments, approvals, updates)' — a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
List activity (comments, approvals, updates) on a pull request. It is categorised as a Read tool in the Bitbucket Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_list_pull_request_activity: 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 Cloud MCP Server. Nothing to install.
bb_list_pull_request_activity 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 bb_list_pull_request_activity 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 bb_list_pull_request_activity. 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.
bb_list_pull_request_activity is provided by the Bitbucket Cloud MCP Server MCP server (or2ooo/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 →