git_cherry_pick · Git MCP: Risk & Policy

WHAT IT DOES

What git_cherry_pick does on Git

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

WHY IT NEEDS A POLICY

Why git_cherry_pick needs a policy

Cherry-pick applies commits from one branch to another, modifying the repository history. This is a Write operation as it creates new commits in the target branch. However, it has high severity because misuse could introduce unintended changes across branches, corrupt history, or cause merge conflicts in shared repositories. It is reversible (can be aborted or reverted), so it doesn't qualify as Destructive.

From the tool's definition Start, continue, or abort cherry-pick

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_cherry_pick Rate-limited

git_cherry_pick 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": {
    "git_cherry_pick": {
      "limits": [
        {
          "counter": "git_cherry_pick_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 Git, so you can run agents against it safely.

FAQ

Questions about git_cherry_pick

What does the git_cherry_pick tool do? +

Start, continue, or abort cherry-pick. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_cherry_pick? +

Register the Git MCP server in PolicyLayer and add a rule for git_cherry_pick: 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. Nothing to install.

What risk level is git_cherry_pick? +

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

Can I rate-limit git_cherry_pick? +

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

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

git_cherry_pick is provided by the Git MCP server (selfagency/git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.