AI agents call get_merge_request_diff to retrieve information from Git MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries merge request diff information without creating, modifying, deleting, or executing anything. Despite the empty description, the tool name strongly indicates a read-only operation that fetches version comparison data. The low severity reflects that diffing merge requests has minimal blast radius—it only exposes code changes for review purposes.
From the tool's definition Tool name 'get_merge_request_diff' indicates retrieval of diff data from a merge request. The 'get_' prefix and 'diff' (a read-only comparison output) suggest no side effects or modifications.
Documented attack patterns abuse exactly the kind of access get_merge_request_diff gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_merge_request_diff:
{
"version": "1",
"default": "deny",
"tools": {
"get_merge_request_diff": {}
}
}get_merge_request_diff 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.
get_merge_request_diff. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for get_merge_request_diff: 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 Git MCP Server. Nothing to install.
get_merge_request_diff 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_diff 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_diff. 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_diff is provided by the Git MCP Server MCP server (yumeminami/git_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 Git MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.