create_mr_approval_rule · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_mr_approval_rule does on Mcp Gitlab

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

This tool creates new approval rules that enforce code review requirements on merge requests. While reversible (Write, not Destructive), it has high severity because misconfigured approval rules could bypass security controls, weaken code review enforcement, or lock reviewers out of merging critical changes. The dry_run safety feature mitigates some risk but does not change the underlying write capability.

From the tool's definition Tool creates a project-level MR approval rule, as stated in the description. The verb 'Create' indicates data modification. The rule itself is a configuration artifact that modifies project policy but is reversible (can be deleted/modified later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_mr_approval_rule Rate-limited

create_mr_approval_rule 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": {
    "create_mr_approval_rule": {
      "limits": [
        {
          "counter": "create_mr_approval_rule_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 create_mr_approval_rule

What does the create_mr_approval_rule tool do? +

Create a project-level MR approval rule. 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 create_mr_approval_rule? +

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

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

Can I rate-limit create_mr_approval_rule? +

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

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

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