create_draft_pull_request
AI agents use create_draft_pull_request to create or update resources in Bitbucket Server MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket Server MCP environment.
This tool creates a new pull request object (in draft state), which is a reversible write operation. It does not execute code, delete data, or transfer funds. The blast radius is medium because a malicious agent could create many draft PRs to spam the repository or create misleading review states, but the action is reversible via deletion.
From the tool's definition Tool name 'create_draft_pull_request' indicates creation of a pull request in draft status. Sibling tools include 'create_pull_request' and 'convert_to_draft', confirming this creates/modifies review objects.
Attacks that exploit this kind of access
create_draft_pull_request. It is categorised as a Write tool in the Bitbucket Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket Server MCP server in PolicyLayer and add a rule for create_draft_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 Bitbucket Server MCP. Nothing to install.
create_draft_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_draft_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.
Set action: deny in the PolicyLayer policy for create_draft_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.
create_draft_pull_request is provided by the Bitbucket Server MCP server (manpreetshuann/bitbucket-server-mcp). 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 →