AI agents invoke cherry-pick to trigger actions in Python. 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.
Cherry-picking applies commits to a branch, which modifies the git history and working tree. This is an operation that executes a git command with potentially significant side effects on the repository state. While it can be reverted, it triggers an external operation that changes branch state, making Execute the appropriate category.
From the tool's definition Applies specific commits to the current branch... Returns structured data with applied commits, any conflicts, and new commit hash.
Attacks that exploit this kind of access
Applies specific commits to the current branch. Returns structured data with applied commits, any conflicts, and new commit hash. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Python MCP server in PolicyLayer and add a rule for 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 Python. Nothing to install.
cherry-pick is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
cherry-pick is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
cherry-pick is one line of Python's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →