update_pipeline_config · Bitbucket MCP: Risk & Policy

WHAT IT DOES

What update_pipeline_config does on Bitbucket

AI agents use update_pipeline_config 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_pipeline_config needs a policy

This tool modifies pipeline configuration settings in a Bitbucket repository, which is a reversible change. While disabling pipelines could impact CI/CD workflows and has a significant blast radius (high severity), it does not permanently delete data or cause irreversible destruction.

From the tool's definition Tool name 'update_pipeline_config' with description stating it can 'enable or disable pipelines' indicates modification of configuration state. The action is reversible—pipelines can be toggled on and off—making it a write operation rather than destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pipeline_config Rate-limited

update_pipeline_config 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_pipeline_config": {
      "limits": [
        {
          "counter": "update_pipeline_config_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_pipeline_config

What does the update_pipeline_config tool do? +

Update pipeline configuration for a repository (enable or disable pipelines). 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_pipeline_config? +

Register the Bitbucket MCP server in PolicyLayer and add a rule for update_pipeline_config: 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_pipeline_config? +

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

Can I rate-limit update_pipeline_config? +

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

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

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