New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bitbucket_create_pull_request

Create a new pull request in a Bitbucket repository

SERVERSage MCP SOURCEsagemcp/sagemcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/bitbucket-create-pull-request.md

What bitbucket_create_pull_request does on Sage MCP

AI agents use bitbucket_create_pull_request to create or update resources in Sage MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.

Why bitbucket_create_pull_request is rated Medium

This tool creates a new pull request, which is a reversible modification to a repository's state. It does not execute arbitrary code, delete data irreversibly, or move money. It falls squarely into the Write category.

From the tool's definition Tool name is 'bitbucket_create_pull_request' and description states 'Create a new pull request in a Bitbucket repository'. The verb 'Create' and 'new' indicate data creation that is reversible (pull requests can be closed/deleted).

Questions about bitbucket_create_pull_request

What does the bitbucket_create_pull_request tool do? +

Create a new pull request in a Bitbucket repository. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bitbucket_create_pull_request? +

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

What risk level is bitbucket_create_pull_request? +

bitbucket_create_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bitbucket_create_pull_request? +

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

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

bitbucket_create_pull_request is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.