update_merge_request_tool · MCP Gitlab MCP: Risk & Policy

WHAT IT DOES

What update_merge_request_tool does on MCP Gitlab

AI agents use update_merge_request_tool 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_tool needs a policy

Merge request updates are reversible write operations that can modify titles, descriptions, assignees, labels, milestones, or approval status. While not destructive, they affect CI/CD workflows and code integration decisions. Severity is high due to potential impact on deployment pipelines and team coordination, though the blast radius is contained to merge request metadata rather than code or production systems.

From the tool's definition Tool name 'update_merge_request_tool' indicates modification of merge request state or metadata. On a GitLab server, merge requests are central to code review and integration workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_merge_request_tool Rate-limited

update_merge_request_tool 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_tool": {
      "limits": [
        {
          "counter": "update_merge_request_tool_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_tool

What does the update_merge_request_tool tool do? +

update_merge_request_tool. 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_tool? +

Register the MCP Gitlab MCP server in PolicyLayer and add a rule for update_merge_request_tool: 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_tool? +

update_merge_request_tool 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_tool? +

Yes. Add a rate_limit block to the update_merge_request_tool 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_tool completely? +

Set action: deny in the PolicyLayer policy for update_merge_request_tool. 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_tool? +

update_merge_request_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.