AI agents use updatePullRequest 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.
This tool modifies pull request state reversibly—updating properties like title, description, reviewers, or status. While it changes data, it does not irreversibly destroy data (ruling out Destructive) and does not execute arbitrary code (ruling out Execute). It is a reversible Write operation with medium severity since a misused update could disrupt collaboration workflows, though changes can be undone or corrected.
From the tool's definition Tool name 'updatePullRequest' and description 'Update a pull request' indicate modification of existing pull request data.
Documented attack patterns abuse exactly the kind of access updatePullRequest 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 updatePullRequest:
{
"version": "1",
"default": "deny",
"tools": {
"updatePullRequest": {
"limits": [
{
"counter": "updatepullrequest_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}updatePullRequest 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.
Update a pull request. 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 updatePullRequest: 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.
updatePullRequest 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 updatePullRequest 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 updatePullRequest. 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.
updatePullRequest 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.