This record as markdown: /tools/io-github-zereight-gitlab-mcp/delete-draft-note.md
What delete_draft_note does on Gitlab Mcp
AI agents call delete_draft_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_draft_note is rated Critical
This tool permanently removes a draft note, which cannot be undone. Although the blast radius is limited to a single draft note (not production code or published content), it is an irreversible destructive action. Severity is medium rather than high because draft notes are typically temporary, unpublished artifacts with lower operational impact compared to deletion of published content, commits, or branches.
From the tool's definition Tool name is 'delete_draft_note' with description 'Delete a draft note'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_draft_note 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_draft_note, this is the rule to start with:
delete_draft_note is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every delete_draft_note call is checked against it from then on.
Questions about delete_draft_note
Delete a draft note. 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.
Register the Gitlab MCP server in PolicyLayer and add a rule for delete_draft_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.
delete_draft_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_draft_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_draft_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_draft_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.
Across the catalogue