create_draft_note
Create a draft note for a merge request
This record as markdown: /tools/io-github-zereight-gitlab-mcp/create-draft-note.md
What create_draft_note does on Gitlab Mcp
AI agents use create_draft_note to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.
Why create_draft_note is rated Medium
This tool creates a new draft note, which is a reversible write operation. Draft notes are not published comments and can be deleted or modified, so it is classified as Write rather than Execute or Destructive.
From the tool's definition Tool name 'create_draft_note' and description 'Create a draft note for a merge request' indicate the tool creates new data (a draft note) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs create_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 create_draft_note, this is the rule to start with:
create_draft_note stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every create_draft_note call is checked against it from then on.
Questions about create_draft_note
Create a draft note for a merge request. It is categorised as a Write tool in the Gitlab Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for create_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.
create_draft_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue