AI agents use gitlab_merge_requests to create or update resources in Gitlab Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Api environment.
Merge requests in GitLab are used to propose, review, and integrate code changes. While the description is empty, the tool name and context indicate write capability (creating or modifying merge requests). This is categorized as Write rather than Execute because merge requests are data objects that represent proposed changes rather than direct code execution.
From the tool's definition Tool is named gitlab_merge_requests with no description provided. Based on GitLab API conventions, merge request operations typically create, update, or modify code integration state.
Documented attack patterns abuse exactly the kind of access gitlab_merge_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab Api, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_merge_requests:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_merge_requests": {
"limits": [
{
"counter": "gitlab_merge_requests_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gitlab_merge_requests 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.
gitlab_merge_requests. It is categorised as a Write tool in the Gitlab Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab Api MCP server in PolicyLayer and add a rule for gitlab_merge_requests: 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 Api. Nothing to install.
gitlab_merge_requests 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 gitlab_merge_requests 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 gitlab_merge_requests. 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.
gitlab_merge_requests is provided by the Gitlab Api MCP server (knuckles-team/gitlab-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitlab Api, 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.
26 Gitlab Api tools catalogued and risk-classified — across an index of 43,000+ MCP servers.