unapprove_merge_request · Kepler MCP GitLab Server MCP

WHAT IT DOES

What unapprove_merge_request does on Kepler MCP GitLab Server

AI agents use unapprove_merge_request to create or update resources in Kepler MCP GitLab Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kepler MCP GitLab Server environment.

WHY IT NEEDS A POLICY

Why unapprove_merge_request needs a policy

Unapproving a merge request is a write operation that modifies merge request state/metadata without permanently deleting or destroying data. It is reversible—an approval can be re-added. This is less severe than destructive operations (which cannot be undone) but more severe than read operations.

From the tool's definition Tool name 'unapprove_merge_request' indicates it modifies the approval state of a merge request, a reversible change to repository metadata. Description is empty, limiting evidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unapprove_merge_request Rate-limited

unapprove_merge_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unapprove_merge_request": {
      "limits": [
        {
          "counter": "unapprove_merge_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kepler MCP GitLab Server, so you can run agents against it safely.

FAQ

Questions about unapprove_merge_request

What does the unapprove_merge_request tool do? +

unapprove_merge_request. It is categorised as a Write tool in the Kepler MCP GitLab Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on unapprove_merge_request? +

Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for unapprove_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 Kepler MCP GitLab Server. Nothing to install.

What risk level is unapprove_merge_request? +

unapprove_merge_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit unapprove_merge_request? +

Yes. Add a rate_limit block to the unapprove_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.

How do I block unapprove_merge_request completely? +

Set action: deny in the PolicyLayer policy for unapprove_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.

What MCP server provides unapprove_merge_request? +

unapprove_merge_request is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.