Low Risk

getPendingReviewPRs

List all open pull requests in the workspace where the authenticated user is a reviewer and has not yet approved.

How to control getPendingReviewPRs ↓

What getPendingReviewPRs does on Bitbucket MCP

AI agents call getPendingReviewPRs to retrieve information from Bitbucket MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getPendingReviewPRs needs a policy

This tool queries and retrieves information about pull requests where the user is a reviewer. It performs no creation, modification, deletion, or execution of code. The action is purely informational—listing existing PRs that need review. Even in a misuse scenario, the impact is limited to visibility of existing data, making it a standard Read operation with low severity.

From the tool's definition Tool name contains 'get' and description states 'List all open pull requests' — retrieves data without modification. Returns pending review assignments in read-only fashion.

Documented attack patterns abuse exactly the kind of access getPendingReviewPRs gives an agent:

How to control getPendingReviewPRs

PolicyLayer is an MCP gateway — it sits between your AI agents and Bitbucket MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getPendingReviewPRs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getPendingReviewPRs": {}
  }
}

getPendingReviewPRs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Bitbucket MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getPendingReviewPRs

What does the getPendingReviewPRs tool do? +

List all open pull requests in the workspace where the authenticated user is a reviewer and has not yet approved. It is categorised as a Read tool in the Bitbucket MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getPendingReviewPRs? +

Register the Bitbucket MCP server in PolicyLayer and add a rule for getPendingReviewPRs: 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 MCP. Nothing to install.

What risk level is getPendingReviewPRs? +

getPendingReviewPRs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getPendingReviewPRs? +

Yes. Add a rate_limit block to the getPendingReviewPRs 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.

How do I block getPendingReviewPRs completely? +

Set action: deny in the PolicyLayer policy for getPendingReviewPRs. 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.

What MCP server provides getPendingReviewPRs? +

getPendingReviewPRs is provided by the Bitbucket MCP server (matanyemini/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bitbucket MCP tool call.

Start from Bitbucket MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

49 Bitbucket MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.