// MCP TOOL REFERENCE

gitlab_delete_release

Delete the release record for tag_name permanently. Irreversible for the release entry. Requires tag_name. Recommended pre-check: gitlab_get_release or gitlab_list_releases.

ServerGitlab
CategoryDestructive

How to control gitlab_delete_release ↓

WHAT IT DOES

What gitlab_delete_release does on Gitlab

AI agents call gitlab_delete_release to permanently remove resources in Gitlab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why gitlab_delete_release needs a policy

This tool permanently and irreversibly deletes a release record from GitLab. The description explicitly states 'permanently' and 'Irreversible', which are defining characteristics of Destructive actions. While it only removes the release metadata (not the underlying git tag necessarily), it is still destructive to the release artifact and cannot be undone.

From the tool's definition Delete the release record for tag_name permanently. Irreversible for the release entry.

Documented attack patterns abuse exactly the kind of access gitlab_delete_release gives an agent:

POLICY

How to control gitlab_delete_release

PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_delete_release:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gitlab_delete_release"
  ]
}

gitlab_delete_release disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Gitlab — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Gitlab tools

Destructive gitlab_delete_branch Delete a repository branch permanently. Requires branch. Recommended pre-check: gitlab_get Destructive gitlab_delete_draft_note Delete a merge-request draft note permanently. Irreversible. Requires merge_request_iid an Destructive gitlab_delete_group_wiki_page Delete a group wiki page permanently. Irreversible. Requires group_id and slug. Recommende Destructive gitlab_delete_issue Delete an issue permanently. Irreversible. Requires issue_iid. Recommended pre-check: gitl Destructive gitlab_delete_issue_emoji_reaction Delete an emoji reaction from an issue permanently. Irreversible for that reaction. Requir Destructive gitlab_delete_issue_link Delete an issue link permanently. Irreversible for that relation. Requires issue_iid and i Destructive gitlab_delete_issue_note_emoji_reaction Delete an emoji reaction from an issue note permanently. Irreversible for that reaction. R Destructive gitlab_delete_label Delete a label permanently. Irreversible. Requires name or label_id. Recommended pre-check

All 190 Gitlab tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Gitlab → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gitlab_delete_release

What does the gitlab_delete_release tool do? +

Delete the release record for tag_name permanently. Irreversible for the release entry. Requires tag_name. Recommended pre-check: gitlab_get_release or gitlab_list_releases. It is categorised as a Destructive tool in the Gitlab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gitlab_delete_release? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_delete_release: 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 Gitlab. Nothing to install.

What risk level is gitlab_delete_release? +

gitlab_delete_release is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gitlab_delete_release? +

Yes. Add a rate_limit block to the gitlab_delete_release 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.

How do I block gitlab_delete_release completely? +

Set action: deny in the PolicyLayer policy for gitlab_delete_release. 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.

What MCP server provides gitlab_delete_release? +

gitlab_delete_release is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gitlab tool call.

Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.