Bitbucket MCP

49 tools. 23 can modify or destroy data without limits.

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

Last updated:

23 can modify or destroy data
26 read-only
49 tools total

Community server · catalogue entry verified 11/06/2026

How to control Bitbucket MCP ↓

What Bitbucket MCP exposes to your agents

Read (26) Write / Execute (21) Destructive / Financial (2)
Critical Risk

The most dangerous Bitbucket MCP tools

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

How to control Bitbucket MCP

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

Deny destructive operations
{
  "deletePullRequestComment": {
    "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
{
  "unapprovePullRequest": {
    "limits": [
      {
        "counter": "unapprovepullrequest_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "getEffectiveDefaultReviewers": {
    "limits": [
      {
        "counter": "geteffectivedefaultreviewers_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Bitbucket MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON BITBUCKET →

Free to start. No card required.

All 49 Bitbucket MCP tools

READ 26 tools
Read getEffectiveDefaultReviewers Get effective default reviewers for a repository Read getEffectiveRepositoryBranchingModel Get the effective branching model for a repository Read getPendingReviewPRs List all open pull requests in the workspace where the authenticated user is a reviewer and has not yet approv Read getPipelineRun Get details for a specific pipeline run Read getPipelineStep Get details for a specific pipeline step Read getPipelineStepLogs Get logs for a specific pipeline step Read getPipelineSteps List steps for a pipeline run Read getProjectBranchingModel Get the branching model for a project Read getProjectBranchingModelSettings Get the branching model config for a project Read getPullRequest Get details for a specific pull request Read getPullRequestActivity Get activity log for a pull request Read getPullRequestComment Get a specific comment on a pull request Read getPullRequestComments List comments on a pull request Read getPullRequestCommits Get commits on a pull request Read getPullRequestDiff Get diff for a pull request Read getPullRequestDiffStat Get diff statistics for a pull request Read getPullRequestPatch Get patch for a pull request Read getPullRequests Get pull requests for a repository Read getPullRequestStatuses List commit statuses associated with a pull request Read getPullRequestTask Get a specific task on a pull request Read getPullRequestTasks List tasks on a pull request Read getRepository Get repository details Read getRepositoryBranchingModel Get the branching model for a repository Read getRepositoryBranchingModelSettings Get the branching model config for a repository Read listPipelineRuns List pipeline runs for a repository Read listRepositories List Bitbucket repositories

Related servers

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

Questions about Bitbucket MCP

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

Yes. The Bitbucket MCP server exposes 2 destructive tools including deletePullRequestComment, deletePullRequestTask. 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 MCP? +

The Bitbucket MCP server has 19 write tools including unapprovePullRequest, declinePullRequest, addPendingPullRequestComment. 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 MCP.

How many tools does the Bitbucket MCP server expose? +

49 tools across 4 categories: Destructive, Execute, Read, Write. 26 are read-only. 23 can modify, create, or delete data.

How do I enforce a policy on Bitbucket MCP? +

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

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.