// SCAN REPORT

Mcp Bitbucket Server

18 tools. 8 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

8 can modify or destroy data

10 read-only

18 tools total

Community server · catalogue entry verified 29/06/2026

How to control Mcp Bitbucket Server ↓

TOOL MAP

What Mcp Bitbucket Server exposes to your agents

Read (10) Write / Execute (6) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mcp Bitbucket Server tools

Destructive · High delete_pr_comment This tool irreversibly deletes pull request comments, which cannot be undone. Destructive · Low remove_pr_comment_reaction The tool irreversibly removes a reaction from a PR comment. Write · Medium add_pr_comment This tool creates new comments on pull requests, which is a reversible write operation. Write · Low add_pr_comment_reaction This tool modifies state by adding a reaction to a comment, making it a Write operation rather than Read.

8 of Mcp Bitbucket Server's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mcp Bitbucket Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Bitbucket Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_pr_comment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_pr_comment": {
    "limits": [
      {
        "counter": "add_pr_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_all_users": {
    "limits": [
      {
        "counter": "get_all_users_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mcp Bitbucket Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP BITBUCKET →

Instant setup, no code required.

FULL CATALOGUE

All 18 Mcp Bitbucket Server tools

DESTRUCTIVE 2 tools

Destructive delete_pr_comment Delete a pull request comment. You can delete your own comments. Only REPO_ADMIN users can delete comments cre Destructive remove_pr_comment_reaction Remove an emoticon reaction from a pull request comment. Only the user who added the reaction can remove it. S

WRITE 6 tools

Write add_pr_comment Add a general comment to a pull request (not attached to any specific file or line). Use parentId to reply to Write add_pr_comment_reaction Add an emoticon reaction to a pull request comment. Supported emoticons: thumbsup, thumbsdown, heart, thinking Write add_pr_file_comment Add a comment attached to a specific file in a pull request (not to a specific line). The comment will appear Write add_pr_line_comment Add an inline comment to a specific line in a pull request. Use the line numbers from get_pull_request_file_di Write create_pull_request Create a new pull request from a source branch to a target branch. Accepts simple branch names (e.g., Write update_review_status Change the review status for a pull request. Sets the authenticated user\

READ 10 tools

Read get_all_users Retrieve a page of users from Bitbucket Server, optionally filtered by search term Read get_inbox_pull_requests Returns pull requests in the authenticated user Read get_pull_request Retrieve full details for a pull request including title, description, author, state, source branch (fromRef), Read get_pull_request_activities Gets activity on a pull request including comments, approvals, merges, reviews, and updates. Can optionally fi Read get_pull_request_changes Gets a list of all changed files in a pull request with file-level metadata (file paths, change types like ADD Read get_pull_request_diff Retrieve diff for a pull request. Omit the path parameter to get the full PR diff, or specify a file path to g Read get_pull_request_file_diff Gets a structured line-by-line diff for a specific file in a pull request. Returns JSON with hunks, segments, Read get_user_profile Gets Bitbucket Server user profile details by username Read list_projects Retrieve a page of projects. Only projects for which the authenticated user has PROJECT_VIEW permission will b Read list_repositories List all repositories in a Bitbucket Server project

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Mcp Bitbucket Server

Can an AI agent delete data through the Mcp Bitbucket Server MCP server? +

Yes. The Mcp Bitbucket Server server exposes 2 destructive tools including delete_pr_comment, remove_pr_comment_reaction. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mcp Bitbucket Server? +

The Mcp Bitbucket Server server has 6 write tools including add_pr_comment, add_pr_comment_reaction, add_pr_file_comment. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Bitbucket Server.

How many tools does the Mcp Bitbucket Server MCP server expose? +

18 tools across 3 categories: Destructive, Read, Write. 10 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on Mcp Bitbucket Server? +

Register the Mcp Bitbucket Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mcp Bitbucket Server tool call.

Deterministic rules across all 18 Mcp Bitbucket Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP BITBUCKET →

Instant setup, no code required.

18 Mcp Bitbucket Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.