Publish a draft pull request to make it ready for review
AI agents use publishDraftPullRequest to create or update resources in Bitbucket MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket MCP environment.
Publishing a draft pull request modifies the state and visibility of a code review artifact, enabling it for team review and potential merging. While this is a state change to important development infrastructure, it is reversible (can be converted back to draft, as evidenced by the sibling tool 'convertTodraft').
From the tool's definition Tool description states 'Publish a draft pull request to make it ready for review' — this changes the state of a pull request from draft to published, which is a reversible modification of data.
Documented attack patterns abuse exactly the kind of access publishDraftPullRequest gives an agent:
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 publishDraftPullRequest:
{
"version": "1",
"default": "deny",
"tools": {
"publishDraftPullRequest": {
"limits": [
{
"counter": "publishdraftpullrequest_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}publishDraftPullRequest stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Publish a draft pull request to make it ready for review. It is categorised as a Write tool in the Bitbucket MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket MCP server in PolicyLayer and add a rule for publishDraftPullRequest: 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.
publishDraftPullRequest 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 publishDraftPullRequest 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 publishDraftPullRequest. 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.
publishDraftPullRequest 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.
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.