New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_list_mr_discussions

List discussions (comment threads) on a merge request

SERVERSage MCP SOURCEsagemcp/sagemcp
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/sagemcp-sagemcp/gitlab-list-mr-discussions.md

What gitlab_list_mr_discussions does on Sage MCP

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

Why gitlab_list_mr_discussions is rated Low

This tool retrieves existing discussion data from GitLab merge requests without creating, modifying, or deleting any data. It is a straightforward query operation that presents minimal security risk, as the worst-case misuse is unauthorized viewing of comments that an attacker already has access to (they can create MRs and presumably read discussions). Classification as Read with low severity is appropriate.

From the tool's definition Tool name includes 'list' and description states it 'List discussions (comment threads) on a merge request' — a retrieval operation with no modification or side effects.

Questions about gitlab_list_mr_discussions

What does the gitlab_list_mr_discussions tool do? +

List discussions (comment threads) on a merge request. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gitlab_list_mr_discussions? +

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

What risk level is gitlab_list_mr_discussions? +

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

Can I rate-limit gitlab_list_mr_discussions? +

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

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

gitlab_list_mr_discussions is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.