Permanently delete an attachment from a repository.
AI agents call delete_attachment to permanently remove resources in Bitbucket Server MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data (an attachment) with no undo capability, matching the Destructive category definition. While the blast radius is limited to a single attachment rather than entire repositories or critical files, permanent deletion of repository artifacts (which may include documentation, images, or other supporting materials) constitutes a high-severity risk if misused by an AI agent.
From the tool's definition Permanently delete an attachment from a repository.
Attacks that exploit this kind of access
Permanently delete an attachment from a repository. It is categorised as a Destructive tool in the Bitbucket Server MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbucket Server MCP server in PolicyLayer and add a rule for delete_attachment: 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 Server MCP. Nothing to install.
delete_attachment 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 delete_attachment 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 delete_attachment. 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.
delete_attachment is provided by the Bitbucket Server MCP server (manpreetshuann/bitbucket-server-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 →