Apply and remove a stash. Applies the specified stash to the working directory and then removes it from the stash stack. Combines the apply and drop operations.
AI agents call git_stash_pop to permanently remove resources in Git MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
git_stash_pop irreversibly removes the stash entry from the stash stack. While the changes are re-applied to the working directory, the stash itself is permanently dropped and cannot be recovered through normal means if something goes wrong (e.g., merge conflict or subsequent discard). The destructive aspect (drop) dominates over the write aspect (apply), making this Destructive.
From the tool's definition 'Apply and remove a stash' and 'removes it from the stash stack' — the stash entry is permanently deleted after being applied. 'Combines the apply and drop operations.'
Attacks that exploit this kind of access
Apply and remove a stash. Applies the specified stash to the working directory and then removes it from the stash stack. Combines the apply and drop operations. It is categorised as a Destructive tool in the Git MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_stash_pop: 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_stash_pop is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the git_stash_pop 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_stash_pop. 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_stash_pop 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 →