set_merge_request_title · GitLab MR MCP: Risk & Policy

WHAT IT DOES

What set_merge_request_title does on GitLab MR MCP

AI agents use set_merge_request_title to create or update resources in GitLab MR MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MR MCP environment.

WHY IT NEEDS A POLICY

Why set_merge_request_title needs a policy

This tool modifies merge request data (the title) in a reversible manner. It is a Write operation because it creates or updates data without irreversible deletion. Severity is medium because changing a merge request title could cause confusion about PR intent or history, but the action is easily reversible and has limited blast radius compared to merging code or deleting data.

From the tool's definition Tool name is 'set_merge_request_title' and description states it 'Set the title of a merge request', indicating modification of merge request metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_merge_request_title Rate-limited

set_merge_request_title 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": {
    "set_merge_request_title": {
      "limits": [
        {
          "counter": "set_merge_request_title_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 MR MCP, so you can run agents against it safely.

FAQ

Questions about set_merge_request_title

What does the set_merge_request_title tool do? +

Set the title of a merge request. It is categorised as a Write tool in the GitLab MR MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_merge_request_title? +

Register the GitLab MR MCP server in PolicyLayer and add a rule for set_merge_request_title: 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 MR MCP. Nothing to install.

What risk level is set_merge_request_title? +

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

Can I rate-limit set_merge_request_title? +

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

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

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