delete_release

Delete a release (does not delete the tag)

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/delete-release.md

WHAT IT DOES

What delete_release does on Gitlab Mcp

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

RISK

Why delete_release is rated Critical

This tool irreversibly deletes release data from GitLab, which cannot be undone. While the underlying git tag is preserved, the release object (notes, assets, metadata) is permanently removed. This fits the Destructive category—actions that cannot be undone.

From the tool's definition Tool name is 'delete_release' and description states 'Delete a release (does not delete the tag)'. The verb 'Delete' combined with the permanent removal of a release artifact indicates an irreversible destructive action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_release safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_release, this is the rule to start with:

delete_release Hidden

delete_release is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every delete_release call is checked against it from then on.

FAQ

Questions about delete_release

What does the delete_release tool do? +

Delete a release (does not delete the tag). It is categorised as a Destructive tool in the Gitlab Mcp 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 delete_release? +

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

What risk level is delete_release? +

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 delete_release? +

Yes. Add a rate_limit block to the 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 delete_release completely? +

Set action: deny in the PolicyLayer policy for 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 delete_release? +

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

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →