Create a new merge request in a GitLab project
AI agents use create_merge_request to create or update resources in GitLab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MCP Server environment.
This tool creates a new merge request, which modifies project state by introducing a code review object. While merge requests are reversible (they can be closed or declined without merging), their creation can trigger workflows, notifications, and CI/CD pipelines. The severity is medium because misuse could spam notifications or create misleading review requests, but the action is not destructive or financial.
From the tool's definition Tool name is 'create_merge_request' and description states 'Create a new merge request in a GitLab project'. The verb 'Create' and the action of creating a new merge request indicate data creation, which is reversible (merge requests can be closed or deleted).
Documented attack patterns abuse exactly the kind of access create_merge_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_merge_request:
{
"version": "1",
"default": "deny",
"tools": {
"create_merge_request": {
"limits": [
{
"counter": "create_merge_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_merge_request 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.
Free to start. No card required.
Create a new merge request in a GitLab project. It is categorised as a Write tool in the GitLab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for create_merge_request: 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 Server. Nothing to install.
create_merge_request 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_merge_request 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_merge_request. 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_merge_request is provided by the GitLab MCP Server MCP server (radostkali/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitLab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 GitLab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.