AI agents call close_merge_request to permanently remove resources in Git MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing a merge request is generally an irreversible or hard-to-reverse action that discards proposed changes and may close associated workflows. Based on the naming pattern and sibling tools (close_issue, close_milestone all suggest terminal state changes), this is most likely a destructive/irreversible state change.
From the tool's definition Tool name 'close_merge_request' — description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access close_merge_request 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 close_merge_request:
{
"version": "1",
"default": "deny",
"hide": [
"close_merge_request"
]
}close_merge_request disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
close_merge_request. It is categorised as a Destructive tool in the Git MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for close_merge_request: 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.
close_merge_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_merge_request 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 close_merge_request. 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.
close_merge_request 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.