Create a code-review comment on a specific line in an MR
AI agents use create_mr_discussion to create or update resources in Mcp Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitlab environment.
The tool creates new data (a discussion/comment) in GitLab's merge request system. This is a Write operation because it modifies state reversibly—comments are not destructive, do not execute code or commands, and do not move money. The blast radius is low because code-review comments are collaborative, non-destructive additions that do not alter the actual codebase or pipeline execution.
From the tool's definition Tool name 'create_mr_discussion' and description 'Create a code-review comment on a specific line in an MR' indicate creation of a new comment/discussion object. This is a reversible write operation (comments can be edited or deleted).
Attacks that exploit this kind of access
Create a code-review comment on a specific line in an MR. It is categorised as a Write tool in the Mcp Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for create_mr_discussion: 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.
create_mr_discussion 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_mr_discussion 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_mr_discussion. 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_mr_discussion 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 →