// SCAN REPORT

Bitbucket Server MCP

66 tools. 30 can modify or destroy data without limits.

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

Last updated: 30 Jun 2026

30 can modify or destroy data

36 read-only

66 tools total

Community server · catalogue entry verified 30/06/2026

How to control Bitbucket Server MCP ↓

TOOL MAP

What Bitbucket Server MCP exposes to your agents

Read (36) Write / Execute (21) Destructive / Financial (9)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Bitbucket Server MCP tools

Destructive · High delete_attachment The tool irreversibly deletes data (an attachment) with no undo capability, matching the Destructive category definition. Destructive · Medium delete_attachment_metadata The tool performs deletion, which is an irreversible operation that falls into the Destructive category. Destructive · High delete_branch Deleting a branch removes version control history and references irreversibly. Destructive · High delete_project Project deletion is irreversible and has high blast radius—it would remove all associated repositories, pull requests, commits, and configuration.

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

POLICY

How to control Bitbucket Server MCP

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

Deny destructive operations

{
  "delete_attachment": {
    "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_pull_request_comment": {
    "limits": [
      {
        "counter": "add_pull_request_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "browse_files": {
    "limits": [
      {
        "counter": "browse_files_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 Bitbucket Server MCP — 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 BITBUCKET SERVER →

Instant setup, no code required.

FULL CATALOGUE

All 66 Bitbucket Server MCP tools

DESTRUCTIVE 9 tools

Destructive delete_attachment Permanently delete an attachment from a repository. Destructive delete_attachment_metadata Delete the metadata associated with an attachment. Destructive delete_branch delete_branch Destructive delete_project delete_project Destructive delete_pull_request delete_pull_request Destructive delete_pull_request_comment delete_pull_request_comment Destructive delete_pull_request_task delete_pull_request_task Destructive delete_repository delete_repository Destructive delete_tag Delete a tag from a repository. This action is irreversible.

WRITE 21 tools

READ 36 tools

Read browse_files browse_files Read can_merge_pull_request Check whether a pull request can be merged. Read decline_pull_request Decline a pull request. Read find_file find_file Read find_user find_user Read get_attachment Download an attachment from a repository by its numeric ID. Read get_attachment_metadata Retrieve the metadata (JSON) associated with an attachment. Read get_commit Get details of a specific commit. Read get_commit_changes get_commit_changes Read get_commit_diff get_commit_diff Read get_commit_message_suggestion Get a suggested commit message for merging a pull request. Read get_default_branch Get the default branch of a repository. Read get_file_content get_file_content Read get_project Get details of a specific project by its key. Read get_pull_request Get details of a specific pull request. Read get_pull_request_activities get_pull_request_activities Read get_pull_request_comment Get a specific comment on a pull request. Read get_pull_request_diff get_pull_request_diff Read get_pull_request_diff_stat get_pull_request_diff_stat Read get_pull_request_task Get a specific task on a pull request. Read get_repository Get details of a specific repository. Read list_branches list_branches Read list_commits list_commits Read list_dashboard_pull_requests list_dashboard_pull_requests Read list_files list_files Read list_inbox_pull_requests list_inbox_pull_requests Read list_projects List all projects visible to the current user (paginated). Read list_pull_request_comments list_pull_request_comments Read list_pull_request_commits list_pull_request_commits Read list_pull_request_participants list_pull_request_participants Read list_pull_request_tasks List tasks on a pull request (paginated). Read list_pull_requests list_pull_requests Read list_repositories List all repositories in a project (paginated). Read search_code search_code Read unwatch_pull_request Unsubscribe from watching a pull request.

EXPLORE

Related servers

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

FAQ

Questions about Bitbucket Server MCP

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

Yes. The Bitbucket Server MCP server exposes 9 destructive tools including delete_attachment, delete_attachment_metadata, delete_branch. 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 Bitbucket Server MCP? +

The Bitbucket Server MCP server has 21 write tools including add_pull_request_comment, approve_pull_request, convert_to_draft. 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 Bitbucket Server MCP.

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

66 tools across 3 categories: Destructive, Read, Write. 36 are read-only. 30 can modify, create, or delete data.

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

Register the 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 Bitbucket Server MCP tool call.

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

ENFORCE POLICY ON BITBUCKET SERVER →

Instant setup, no code required.

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