get_merge_request_participants
AI agents call get_merge_request_participants 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.
This tool retrieves information about participants in a merge request with no indication of modification, deletion, or execution of code. It queries existing data without side effects. The absence of a description lowers confidence slightly, but the semantic meaning of 'get_' and 'participants' strongly indicates a read operation. No capability to modify, execute, or delete is implied.
From the tool's definition Tool name 'get_merge_request_participants' indicates retrieval of participant data from a merge request. The naming pattern 'get_*' is characteristic of read-only query operations.
Attacks that exploit this kind of access
get_merge_request_participants. 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 get_merge_request_participants: 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.
get_merge_request_participants 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 get_merge_request_participants 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 get_merge_request_participants. 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.
get_merge_request_participants 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 →