stash_pop

THE RISK

Critical Risk

Why stash_pop needs a policy

stash_pop applies the stash contents and then removes (deletes) the stash entry. The removal of the stash is irreversible — once popped, the stash entry is gone. While the applied changes remain in the working tree, the stash record itself is permanently deleted, making this a Destructive operation. Misuse could cause loss of stashed work if conflicts arise during application.

From the tool's definition Apply and remove a stash

Documented attack patterns abuse exactly the kind of access stash_pop gives an agent:

POLICY

How to control stash_pop

PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stash_pop:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "stash_pop"
  ]
}

stash_pop disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Git MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Git MCP Server tools

Destructive branch_delete Delete a branch Destructive remote_remove Remove a remote Destructive tag_delete Delete a tag Execute bulk_action Execute multiple Git operations in sequence. This is the preferred way to execute multiple Execute checkout Switch branches or restore working tree files Write add Stage files Write branch_create Create a new branch Write clone Clone a repository

All 21 Git MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Git MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about stash_pop

What does the stash_pop tool do? +

Apply and remove a stash. 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.

How do I enforce a policy on stash_pop? +

Register the Git MCP Server MCP server in PolicyLayer and add a rule for 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.

What risk level is stash_pop? +

stash_pop is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit stash_pop? +

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

How do I block stash_pop completely? +

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

What MCP server provides stash_pop? +

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

Enforce policy on every Git MCP Server tool call.

Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →