Delete a project-level MR approval rule. dry_run=true by default. This is destructive.
AI agents call delete_mr_approval_rule to permanently remove resources in Mcp Gitlab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an MR approval rule irreversibly removes a control mechanism that enforces code review and quality standards on merge requests. This cannot be undone and affects project governance. Although dry-run is the default (mitigating factor), the tool's primary function is destructive deletion of a configuration object.
From the tool's definition Tool name 'delete_mr_approval_rule' and description states 'Delete a project-level MR approval rule' and explicitly labels it 'This is destructive.'
Attacks that exploit this kind of access
Delete a project-level MR approval rule. dry_run=true by default. This is destructive. It is categorised as a Destructive tool in the Mcp Gitlab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for delete_mr_approval_rule: 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.
delete_mr_approval_rule 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 delete_mr_approval_rule 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 delete_mr_approval_rule. 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.
delete_mr_approval_rule 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.
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 →