bitbucket_list_pull_requests
List pull requests for a Bitbucket repository.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bitbucket-list-pull-requests.md
What bitbucket_list_pull_requests does on UnClick
AI agents call bitbucket_list_pull_requests to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repository slug |
limit | number | — | PRs to return (max 50, default 25) |
state | string | — | Filter by PR state |
username | string | Yes | Bitbucket username |
workspace | string | Yes | Workspace id |
app_password | string | Yes | Bitbucket app password |
Parameters from the server's own tool schema.
Why bitbucket_list_pull_requests is rated Low
This tool queries and retrieves pull request data from a Bitbucket repository. The verb 'list' is characteristic of Read category operations—it fetches existing data without creating, modifying, or deleting anything. No code execution or financial impact is involved.
From the tool's definition Tool name 'bitbucket_list_pull_requests' and description 'List pull requests for a Bitbucket repository' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs bitbucket_list_pull_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitbucket_list_pull_requests, this is the rule to start with:
bitbucket_list_pull_requests is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every bitbucket_list_pull_requests call is checked against it from then on.
Questions about bitbucket_list_pull_requests
List pull requests for a Bitbucket repository. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bitbucket_list_pull_requests accepts 6 parameters: repo, limit, state, username, workspace, app_password. Required: repo, username, workspace, app_password. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for bitbucket_list_pull_requests: 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 UnClick. Nothing to install.
bitbucket_list_pull_requests 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 bitbucket_list_pull_requests 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 bitbucket_list_pull_requests. 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.
bitbucket_list_pull_requests is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue