getPullRequestStatuses

THE RISK

Low Risk

Why getPullRequestStatuses needs a policy

This tool retrieves or queries pull request commit statuses with no side effects. It falls squarely into the Read category as it performs a simple list/fetch operation. The low severity reflects that querying status metadata poses minimal risk to systems and data integrity.

From the tool's definition Tool name 'getPullRequestStatuses' with verb 'get' and description 'List commit statuses' indicate a read-only query operation that retrieves status information without modifying data.

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

POLICY

How to control getPullRequestStatuses

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 getPullRequestStatuses:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getPullRequestStatuses": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bitbucket MCP tools

Destructive deletePullRequestComment Delete a comment on a pull request Destructive deletePullRequestTask Delete a task from a pull request Execute runPipeline Trigger a new pipeline run Execute stopPipeline Stop a running pipeline Write unapprovePullRequest Remove approval from a pull request Write declinePullRequest Decline a pull request Write addPendingPullRequestComment Add a pending (draft) comment to a pull request that can be published later Write addPullRequestComment Add a comment to a pull request (general, inline, or a threaded reply to another comment)

All 49 Bitbucket MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getPullRequestStatuses

What does the getPullRequestStatuses tool do? +

List commit statuses associated with a pull request. 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 getPullRequestStatuses? +

Register the Bitbucket MCP server in PolicyLayer and add a rule for getPullRequestStatuses: 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 getPullRequestStatuses? +

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

Can I rate-limit getPullRequestStatuses? +

Yes. Add a rate_limit block to the getPullRequestStatuses 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 getPullRequestStatuses completely? +

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

getPullRequestStatuses 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.

CHECK YOUR STACK →