Medium Risk

bb_post

Create Bitbucket resources. Returns TOON format by default (token-efficient). IMPORTANT - Cost Optimization: - Use jq param to extract only needed fields from response (e.g., jq: "{id: id, title: title}") - Unfiltered responses include all metadata and are expensive! Output format: TOON (default)...

Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (body)

Part of the Atlassian Bitbucket server.

bb_post can modify Atlassian Bitbucket data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ATLASSIAN BITBUCKET →

Free to start. No card required.

AI agents use bb_post 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_post 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bb_post": {
      "limits": [
        {
          "counter": "bb_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Atlassian Bitbucket policy for all 6 tools.

Get this rule live on your own Atlassian Bitbucket server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ATLASSIAN BITBUCKET →

These attack patterns abuse exactly the kind of access bb_post gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so bb_post only ever does what you allow.

SECURE ATLASSIAN BITBUCKET →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the bb_post tool do? +

Create Bitbucket resources. Returns TOON format by default (token-efficient). IMPORTANT - Cost Optimization: - Use jq param to extract only needed fields from response (e.g., jq: "{id: id, title: title}") - Unfiltered responses include all metadata and are expensive! Output format: TOON (default) or JSON (outputFormat: "json") Common operations: 1. Create PR: /repositories/{workspace}/{repo}/pullrequests body: {"title": "...", "source": {"branch": {"name": "feature"}}, "destination": {"branch": {"name": "main"}}} 2. Add PR comment: /repositories/{workspace}/{repo}/pullrequests/{id}/comments body: {"content": {"raw": "Comment text"}} 3. Approve PR: /repositories/{workspace}/{repo}/pullrequests/{id}/approve body: {} 4. Request changes: /repositories/{workspace}/{repo}/pullrequests/{id}/request-changes body: {} 5. Merge PR: /repositories/{workspace}/{repo}/pullrequests/{id}/merge body: {"merge_strategy": "squash"} (strategies: merge_commit, squash, fast_forward) 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.

How do I enforce a policy on bb_post? +

Register the Atlassian Bitbucket MCP server in PolicyLayer and add a rule for bb_post: 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.

What risk level is bb_post? +

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

Can I rate-limit bb_post? +

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

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

bb_post 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.

Enforce policy on every Atlassian Bitbucket tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.