cherry_pick_commit · Kepler MCP GitLab Server MCP

WHAT IT DOES

What cherry_pick_commit does on Kepler MCP GitLab Server

AI agents invoke cherry_pick_commit to trigger actions in Kepler MCP GitLab Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why cherry_pick_commit needs a policy

Cherry-picking a commit applies changes from one branch to another, which is a non-trivial Git operation that modifies repository state. It is reversible in principle but triggers external operations on the GitLab instance and can cause conflicts or unintended code changes.

From the tool's definition Tool name: cherry_pick_commit — description is empty/uninformative, relying on name alone

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cherry_pick_commit Rate-limited

cherry_pick_commit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cherry_pick_commit": {
      "limits": [
        {
          "counter": "cherry_pick_commit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 cherry_pick_commit

What does the cherry_pick_commit tool do? +

cherry_pick_commit. It is categorised as a Execute tool in the Kepler MCP GitLab Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cherry_pick_commit? +

Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for cherry_pick_commit: 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 cherry_pick_commit? +

cherry_pick_commit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cherry_pick_commit? +

Yes. Add a rate_limit block to the cherry_pick_commit 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 cherry_pick_commit completely? +

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

cherry_pick_commit 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.