list_merge_requests

List merge requests (without project_id: user

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/list-merge-requests.md

WHAT IT DOES

What list_merge_requests does on Gitlab Mcp

AI agents call list_merge_requests to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_merge_requests is rated Low

This tool retrieves/queries merge request data with no side effects. It is a pure read operation matching the 'Read' category definition. Severity is low because listing merge requests has minimal blast radius—it exposes metadata about code review state but does not modify repositories, execute code, or affect financial systems.

From the tool's definition Tool name 'list_merge_requests' and description 'List merge requests' indicate a query operation that retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_merge_requests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_merge_requests, this is the rule to start with:

list_merge_requests Allowed

list_merge_requests is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_merge_requests": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every list_merge_requests call is checked against it from then on.

FAQ

Questions about list_merge_requests

What does the list_merge_requests tool do? +

List merge requests (without project_id: user. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_merge_requests? +

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

What risk level is list_merge_requests? +

list_merge_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_merge_requests? +

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

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

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

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →