update_repository · Bitbucket MCP: Risk & Policy

WHAT IT DOES

What update_repository does on Bitbucket

AI agents use update_repository to create or update resources in Bitbucket — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket environment.

WHY IT NEEDS A POLICY

Why update_repository needs a policy

This tool modifies repository configuration attributes in a reversible manner. While these changes could have cascading effects (visibility changes affect access control, name changes may break integrations), they do not permanently destroy data nor move financial resources. The blast radius is medium because misconfiguration could disrupt repository access or break CI/CD pipelines, but changes can be undone.

From the tool's definition Tool name is 'update_repository' and description states it updates repository settings (project, visibility, description, name) — classic reversible modification of metadata without deletion or destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_repository Rate-limited

update_repository stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_repository": {
      "limits": [
        {
          "counter": "update_repository_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bitbucket, so you can run agents against it safely.

FAQ

Questions about update_repository

What does the update_repository tool do? +

Update repository settings (project, visibility, description, name). It is categorised as a Write tool in the 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 update_repository? +

Register the Bitbucket MCP server in PolicyLayer and add a rule for update_repository: 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 Bitbucket. Nothing to install.

What risk level is update_repository? +

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

Can I rate-limit update_repository? +

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

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

update_repository is provided by the Bitbucket MCP server (javimaligno/mcp-server-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.