Partially update Bitbucket resources. Returns TOON format by default. IMPORTANT - Cost Optimization: Use jq param to filter response fields. Output format: TOON (default) or JSON (outputFormat: "json") Common operations: 1. Update PR title/description: /repositories/{workspace}/{repo}/pullrequest...
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (body)
Part of the Atlassian Bitbucket server.
Free to start. No card required.
AI agents use bb_patch to create or modify resources in Atlassian Bitbucket. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call bb_patch repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Atlassian Bitbucket.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"bb_patch": {
"limits": [
{
"counter": "bb_patch_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Atlassian Bitbucket policy for all 6 tools.
These attack patterns abuse exactly the kind of access bb_patch gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Partially update Bitbucket resources. Returns TOON format by default. IMPORTANT - Cost Optimization: Use jq param to filter response fields. Output format: TOON (default) or JSON (outputFormat: "json") Common operations: 1. Update PR title/description: /repositories/{workspace}/{repo}/pullrequests/{id} body: {"title": "New title", "description": "Updated description"} 2. Update PR reviewers: /repositories/{workspace}/{repo}/pullrequests/{id} body: {"reviewers": [{"uuid": "{user-uuid}"}]} 3. Update repository properties: /repositories/{workspace}/{repo} body: {"description": "New description"} 4. Update comment: /repositories/{workspace}/{repo}/pullrequests/{pr_id}/comments/{comment_id} body: {"content": {"raw": "Updated comment"}} The /2.0 prefix is added automatically. API reference: https://developer.atlassian.com/cloud/bitbucket/rest/. It is categorised as a Write tool in the Atlassian Bitbucket MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian Bitbucket MCP server in PolicyLayer and add a rule for bb_patch: 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 Atlassian Bitbucket. Nothing to install.
bb_patch 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 bb_patch 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 bb_patch. 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.
bb_patch is provided by the Atlassian Bitbucket MCP server (@aashari/mcp-server-atlassian-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Atlassian Bitbucket tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.