delete_merge_request_discussion_note

Delete a discussion note on a merge request

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-merge-request-discussion-note.md

What delete_merge_request_discussion_note does on Gitlab Mcp

AI agents call delete_merge_request_discussion_note 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.

Why delete_merge_request_discussion_note is rated Critical

This tool permanently deletes collaboration data (merge request discussion notes) and cannot be undone. While the blast radius is limited to individual notes rather than entire repositories, the irreversible nature and potential to disrupt code review workflows by removing important feedback or context classifies this as Destructive.

From the tool's definition Tool name contains 'delete' and description states 'Delete a discussion note on a merge request'. The action irreversibly removes data (a discussion note).

Questions about delete_merge_request_discussion_note

What does the delete_merge_request_discussion_note tool do? +

Delete a discussion note on a merge request. 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_merge_request_discussion_note? +

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

What risk level is delete_merge_request_discussion_note? +

delete_merge_request_discussion_note 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_merge_request_discussion_note? +

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

How do I block delete_merge_request_discussion_note completely? +

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

What MCP server provides delete_merge_request_discussion_note? +

delete_merge_request_discussion_note 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.

More on Gitlab, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.