Apply changes from specific commits to the current branch. Takes the changes introduced in one or more existing commits and creates new commits with those changes on the current branch.
AI agents use git_cherry_pick to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.
git_cherry_pick modifies the repository by creating new commits that apply existing changes to the current branch. This is a Write operation (reversible modification of data) rather than Destructive because cherry-picked commits can be undone with git reset or git revert. It is not Execute because the tool itself does not run arbitrary code—it applies pre-existing commits.
From the tool's definition Tool description states it 'creates new commits' and 'Apply changes from specific commits to the current branch', indicating modification of repository state through commit creation.
Attacks that exploit this kind of access
Apply changes from specific commits to the current branch. Takes the changes introduced in one or more existing commits and creates new commits with those changes on the current branch. It is categorised as a Write tool in the Git MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Git MCP Server 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 MCP Server. Nothing to install.
git_cherry_pick is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
git_cherry_pick is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). 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 →