AI agents use bb_create_issue to create or update resources in MCP Bitbucket Python — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Bitbucket Python environment.
This tool creates a new issue, which is a reversible write operation. It adds data to the repository's issue tracking system but does not execute code, delete data, or commit financial transactions. The severity is medium because misuse could create numerous spurious issues that clutter tracking systems and waste team resources, but the effect is reversible (issues can be deleted or closed).
From the tool's definition Tool name 'bb_create_issue' and description 'Create an issue in a Bitbucket repository' indicate creation of a new data object (an issue) within a repository tracking system.
Documented attack patterns abuse exactly the kind of access bb_create_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Bitbucket Python, and nothing reaches the server without passing your rules. This is the rule we recommend for bb_create_issue:
{
"version": "1",
"default": "deny",
"tools": {
"bb_create_issue": {
"limits": [
{
"counter": "bb_create_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} bb_create_issue 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.
Free to start. No card required.
Create an issue in a Bitbucket repository. It is categorised as a Write tool in the MCP Bitbucket Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Bitbucket Python MCP server in PolicyLayer and add a rule for bb_create_issue: 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 MCP Bitbucket Python. Nothing to install.
bb_create_issue 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_issue 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_issue. 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_issue is provided by the MCP Bitbucket Python MCP server (kallows/mcp-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Bitbucket Python, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Bitbucket Python tools catalogued and risk-classified — across an index of 43,000+ MCP servers.