update_merge_request · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What update_merge_request does on Mcp Gitlab

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

WHY IT NEEDS A POLICY

Why update_merge_request needs a policy

This tool creates or modifies data reversibly without deleting or executing arbitrary code. While it can affect workflow state and reviewer assignments, the changes are reversible and the dry-run default mitigates misuse risk. Classified as Write rather than Execute because it modifies specific, bounded fields rather than executing arbitrary operations.

From the tool's definition Tool description states it updates merge request properties (title, description, labels, assignees, reviewers) — reversible modifications to existing data. The default dry_run=true safety feature confirms this is intended as a non-destructive write operation.

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 Mcp Gitlab, so you can run agents against it safely.

FAQ

Questions about update_merge_request

What does the update_merge_request tool do? +

Update a merge request (title, description, labels, assignees, reviewers). dry_run=true by default. 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.

How do I enforce a policy on update_merge_request? +

Register the Mcp Gitlab 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 Mcp Gitlab. 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 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.