Delete a label from a GitLab project.
AI agents call delete_label_tool to permanently remove resources in MCP Gitlab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a label is an irreversible action that cannot be undone without manual recreation. While the blast radius is constrained to label metadata (not code or critical infrastructure), the operation permanently destroys data. This meets the Destructive category definition.
From the tool's definition Tool name contains 'delete' and description states 'Delete a label from a GitLab project' — this irreversibly removes a label resource.
Attacks that exploit this kind of access
Delete a label from a GitLab project. It is categorised as a Destructive tool in the MCP Gitlab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Gitlab MCP server in PolicyLayer and add a rule for delete_label_tool: 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 Gitlab. Nothing to install.
delete_label_tool 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_label_tool 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_label_tool. 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_label_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). 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 →