Delete a pipeline variable.
AI agents call delete_pipeline_variable to permanently remove resources in Bitbucket — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes pipeline configuration, which is a destructive action. While not as critical as deleting repositories or code, pipeline variables are essential to CI/CD workflows and their deletion cannot be undone. An AI agent with this capability could disrupt deployments and builds if it deletes variables it shouldn't. High severity is appropriate given the operational impact.
From the tool's definition Tool name contains 'delete' and description states 'Delete a pipeline variable.' Pipeline variables are configuration data that cannot be recovered once deleted.
Attacks that exploit this kind of access
Delete a pipeline variable. It is categorised as a Destructive tool in the Bitbucket MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbucket MCP server in PolicyLayer and add a rule for delete_pipeline_variable: 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.
delete_pipeline_variable 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_pipeline_variable 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_pipeline_variable. 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_pipeline_variable 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.
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 →