list_merge_request_discussions
AI agents call list_merge_request_discussions to retrieve information from Kepler MCP GitLab Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix strongly suggests data retrieval without modification or side effects. Discussions on merge requests are metadata/comments, not executable or destructive. No financial impact. Confidence is reduced to 0.85 due to the missing description, but the semantic meaning of 'list' in API contexts is unambiguously a read operation.
From the tool's definition Tool name 'list_merge_request_discussions' indicates a listing/retrieval operation (list_*). The empty description prevents full certainty, but the naming pattern is consistent with read-only operations like those in the sibling tools (compare_branches,…
Attacks that exploit this kind of access
list_merge_request_discussions. It is categorised as a Read tool in the Kepler MCP GitLab Server MCP Server, which means it retrieves data without modifying state.
Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for list_merge_request_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 Kepler MCP GitLab Server. Nothing to install.
list_merge_request_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 list_merge_request_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 list_merge_request_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.
list_merge_request_discussions is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →