List discussions (comment threads) on a merge request
AI agents call gitlab_list_mr_discussions to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access gitlab_list_mr_discussions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_list_mr_discussions:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_list_mr_discussions": {}
}
}gitlab_list_mr_discussions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
gitlab_list_mr_discussions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.