Delete a tag from a project.
AI agents call delete_tag to permanently remove resources in Kepler MCP GitLab Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a tag is a destructive action that cannot be undone without access to version control history or backups. Tags are typically used to mark releases and important commits; their deletion can disrupt release management, rollback procedures, and team workflows.
From the tool's definition Tool name is 'delete_tag' with description 'Delete a tag from a project.' The verb 'delete' and the description explicitly state permanent removal of a git tag, which is an irreversible operation.
Attacks that exploit this kind of access
Delete a tag from a project. It is categorised as a Destructive tool in the Kepler MCP GitLab Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for delete_tag: 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 Kepler MCP GitLab Server. Nothing to install.
delete_tag 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_tag 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_tag. 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_tag is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). 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 →