mr_discussions

List discussion items for a merge request

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/mr-discussions.md

WHAT IT DOES

What mr_discussions does on Gitlab Mcp

AI agents call mr_discussions 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 mr_discussions is rated Low

This tool retrieves existing discussion data from a merge request without creating, modifying, or deleting anything. It is a straightforward read operation similar to 'list' or 'get' operations. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes discussion metadata without enabling destructive or financial actions.

From the tool's definition Tool name 'mr_discussions' and description 'List discussion items for a merge request' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mr_discussions 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 mr_discussions, this is the rule to start with:

mr_discussions Allowed

mr_discussions 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": {
    "mr_discussions": {}
  }
}

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 mr_discussions call is checked against it from then on.

FAQ

Questions about mr_discussions

What does the mr_discussions tool do? +

List discussion items for a merge request. 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 mr_discussions? +

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

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

Can I rate-limit mr_discussions? +

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

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

mr_discussions 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

The MCP Attack Database →

Guides

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