List the project-level MR approval rules: who must approve, how many approvals are required, applies-to-which-branches.
AI agents call list_mr_approval_rules to retrieve information from Mcp Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves approval rule configuration metadata. It performs a read-only operation that returns information about who must approve merge requests and approval thresholds, but does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal — an attacker gains only visibility into approval policies, not the ability to bypass them or modify merge requests.
From the tool's definition Tool name is 'list_mr_approval_rules' and description states it 'List[s] the project-level MR approval rules' — retrieval of configuration data with no modification or side effects.
Attacks that exploit this kind of access
List the project-level MR approval rules: who must approve, how many approvals are required, applies-to-which-branches. It is categorised as a Read tool in the Mcp Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for list_mr_approval_rules: 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 Mcp Gitlab. Nothing to install.
list_mr_approval_rules 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_mr_approval_rules 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_mr_approval_rules. 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_mr_approval_rules is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_mr_approval_rules is one line of Mcp Gitlab's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →