Delete an existing issue note. This is destructive and cannot be undone. dry_run=true by default.
AI agents call delete_issue_note 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.
This tool permanently removes data (an issue note) with no undo capability. While the blast radius is limited to a single note rather than entire issues/projects, the irreversible nature of deletion places it in the Destructive category rather than Write. The default dry_run=true safety feature mitigates risk somewhat but does not change the fundamental destructive nature of the operation.
From the tool's definition Tool description explicitly states: 'Delete an existing issue note. This is destructive and cannot be undone.' The name contains 'delete' and description confirms irreversible deletion.
Attacks that exploit this kind of access
Delete an existing issue note. This is destructive and cannot be undone. dry_run=true by default. 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_issue_note: 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_issue_note 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_issue_note 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_issue_note. 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_issue_note is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). 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 →