Delete an issue from a Bitbucket repository
AI agents call bb_delete_issue to permanently remove resources in MCP Bitbucket Python — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an issue is an irreversible action that permanently removes issue data, comments, and associated metadata from the repository. This falls squarely into the Destructive category as the operation cannot be undone and represents a significant loss of project information.
From the tool's definition Tool name 'bb_delete_issue' and description 'Delete an issue from a Bitbucket repository' explicitly indicate irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access bb_delete_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_delete_issue:
{
"version": "1",
"default": "deny",
"hide": [
"bb_delete_issue"
]
} bb_delete_issue disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an issue from a Bitbucket repository. It is categorised as a Destructive tool in the MCP Bitbucket Python MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Bitbucket Python MCP server in PolicyLayer and add a rule for bb_delete_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_delete_issue is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bb_delete_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_delete_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_delete_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.