list_pull_request_statuses
AI agents call list_pull_request_statuses to retrieve information from MCP Atlassian + Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name clearly denotes listing/retrieving pull request status data, which is a non-destructive query operation. It does not modify, execute, or delete anything. While the lack of description reduces absolute confidence slightly, the 'list_' prefix strongly suggests a Read operation consistent with Bitbucket API patterns for inspecting PR workflow statuses.
From the tool's definition Tool name 'list_pull_request_statuses' indicates retrieval of status information about pull requests. The verb 'list' is a classic Read operation pattern.
Attacks that exploit this kind of access
list_pull_request_statuses. It is categorised as a Read tool in the MCP Atlassian + Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian + Bitbucket MCP server in PolicyLayer and add a rule for list_pull_request_statuses: 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 MCP Atlassian + Bitbucket. Nothing to install.
list_pull_request_statuses 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_pull_request_statuses 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_pull_request_statuses. 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_pull_request_statuses is provided by the MCP Atlassian + Bitbucket MCP server (jellythomas/mcp-atlassian-with-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 →