update_merge_request · GitLab MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_merge_request does on GitLab MCP Server

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_merge_request needs a policy

The tool modifies merge request attributes (title, description, target branch, assignees, labels, etc.) reversibly without deleting data or executing arbitrary code. This is a Write operation. Severity is medium because unauthorized updates to merge requests could delay code reviews, alter review scope, or manipulate CI/CD workflows, but changes are not permanent and can be undone by authorized users.

From the tool's definition Tool name 'update_merge_request' combined with description '更新 Merge Request' (Chinese for 'Update Merge Request') indicates modification of existing merge request data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_merge_request Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_merge_request": {
      "limits": [
        {
          "counter": "update_merge_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitLab MCP Server, so you can run agents against it safely.

FAQ

Questions about update_merge_request

What does the update_merge_request tool do? +

更新 Merge Request. 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.

How do I enforce a policy on update_merge_request? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_merge_request? +

update_merge_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_merge_request? +

Yes. Add a rate_limit block to the update_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.

How do I block update_merge_request completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_merge_request? +

update_merge_request is provided by the GitLab MCP Server MCP server (snowild/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.