delete_issue_link

Delete an issue link

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-issue-link.md

WHAT IT DOES

What delete_issue_link does on Gitlab Mcp

AI agents call delete_issue_link 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_issue_link is rated Critical

This tool permanently removes an issue link relationship in GitLab. While the scope is limited (a link, not the issue itself), the action is irreversible and represents data destruction. This qualifies as Destructive rather than Write, as deletion cannot be undone without manual restoration.

From the tool's definition Tool name: 'delete_issue_link' with description 'Delete an issue link'. The word 'delete' indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_issue_link 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_issue_link, this is the rule to start with:

delete_issue_link Hidden

delete_issue_link 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_issue_link"
  ]
}

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_issue_link call is checked against it from then on.

FAQ

Questions about delete_issue_link

What does the delete_issue_link tool do? +

Delete an issue link. 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_issue_link? +

Register the Gitlab MCP server in PolicyLayer and add a rule for delete_issue_link: 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_issue_link? +

delete_issue_link 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_issue_link? +

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

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

delete_issue_link 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

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

Guides

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