git_stash_drop

Elimina un stash. Parametros: index (int, default 0).

SERVERMCP Framework Personal SOURCEinggerman/mcps

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/git-stash-drop.md

WHAT IT DOES

What git_stash_drop does on MCP Framework Personal

AI agents call git_stash_drop to permanently remove resources in MCP Framework Personal, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why git_stash_drop is rated Critical

An AI agent that decides to call git_stash_drop doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from MCP Framework Personal is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_stash_drop safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_stash_drop, this is the rule to start with:

git_stash_drop Hidden

git_stash_drop is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every git_stash_drop call is checked against it from then on.

FAQ

Questions about git_stash_drop

What does the git_stash_drop tool do? +

Elimina un stash. Parametros: index (int, default 0). It is categorised as a Destructive tool in the MCP Framework Personal 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 git_stash_drop? +

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

What risk level is git_stash_drop? +

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

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

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

git_stash_drop is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 643 MCP Framework Personal tools → Critical-risk tools on this server →

Across the catalogue

delete_git_repo on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →