get_merge_request_changes
AI agents call get_merge_request_changes 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 tool fetches and displays changes associated with a merge request—a purely informational operation with no side effects. Even though the description is empty, the tool name unambiguously indicates data retrieval ('get') of immutable historical change information. No write, execute, destructive, or financial impact is possible.
From the tool's definition Tool name 'get_merge_request_changes' indicates retrieval of merge request diff/changes data without modification.
Attacks that exploit this kind of access
get_merge_request_changes. 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_changes: 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_changes 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_changes 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_changes. 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_changes 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 →