List merge requests in a project. State can be 'opened', 'closed', 'merged', or 'all'
AI agents call list_merge_requests 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 displays existing merge request data without creating, modifying, or deleting anything. It is a read-only operation with minimal blast radius—misuse would only expose or enumerate merge requests the agent already has access to, not cause irreversible changes or financial impact.
From the tool's definition Tool name 'list_merge_requests' and description 'List merge requests in a project' indicate a query/retrieval operation with no side effects. The state parameter ('opened', 'closed', 'merged', 'all') is filtering only, not modifying data.
Documented attack patterns abuse exactly the kind of access list_merge_requests 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 list_merge_requests:
{
"version": "1",
"default": "deny",
"tools": {
"list_merge_requests": {}
}
}list_merge_requests 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 merge requests in a project. State can be 'opened', 'closed', 'merged', or 'all'. 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 list_merge_requests: 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.
list_merge_requests 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_requests 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_requests. 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_requests 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.