Create or update files in a Bitbucket repository by creating a new commit
AI agents use bb_create_commit_files to create or update resources in Bitbucket Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket Cloud MCP Server environment.
This tool modifies repository content by creating commits that add or update files. While reversible through subsequent commits, it directly changes the repository state and could be misused to introduce malicious code, inject vulnerabilities, or corrupt project files.
From the tool's definition Tool creates or updates files in a repository by creating a new commit. The description explicitly states 'create or update files', which are write operations.
Attacks that exploit this kind of access
Create or update files in a Bitbucket repository by creating a new commit. It is categorised as a Write tool in the Bitbucket Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_create_commit_files: 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 Cloud MCP Server. Nothing to install.
bb_create_commit_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bb_create_commit_files 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.
Set action: deny in the PolicyLayer policy for bb_create_commit_files. 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.
bb_create_commit_files is provided by the Bitbucket Cloud MCP Server MCP server (or2ooo/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →