Critical Risk →

stash

Pushes, pops, applies, drops, shows, or clears stash entries. Returns structured result with action, success, message, and stash reference.

How to control stash ↓

What stash does on Github

AI agents call stash to permanently remove resources in Github — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why stash needs a policy

The tool supports 'drop' and 'clear' operations on stash entries, which irreversibly delete stash data. These operations cannot be undone (git stash drop/clear permanently removes stashed changes). While push/pop/apply are reversible Write/Execute operations, the most severe applicable category due to 'drops' and 'clears' is Destructive.

From the tool's definition drops, clears stash entries

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

How to control stash

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "stash"
  ]
}

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

  1. Create a free account and register Github — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about stash

What does the stash tool do? +

Pushes, pops, applies, drops, shows, or clears stash entries. Returns structured result with action, success, message, and stash reference. It is categorised as a Destructive tool in the Github 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? +

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

What risk level is stash? +

stash 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? +

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

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

stash is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Github tool call.

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

Free to start. No card required.

202 Github tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.