git_stash_apply

Aplica un stash sin eliminarlo. Parametros: index (int, default 0).

SERVERMCP Framework Personal SOURCEinggerman/mcps

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What git_stash_apply does on MCP Framework Personal

AI agents invoke git_stash_apply to trigger actions in MCP Framework Personal. 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.

RISK

Why git_stash_apply is rated High

Applying a git stash modifies the working tree and index by restoring stashed changes. This is an external VCS operation that changes file state, making it Execute. It is not purely destructive since the stash entry is preserved, but it does trigger external file system and git operations whose effects depend on the stash content.

From the tool's definition 'Aplica un stash sin eliminarlo' — applies a git stash entry to the working directory

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_stash_apply 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_apply, this is the rule to start with:

git_stash_apply Rate-limited

git_stash_apply stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_stash_apply": {
      "limits": [
        {
          "counter": "git_stash_apply_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_apply call is checked against it from then on.

FAQ

Questions about git_stash_apply

What does the git_stash_apply tool do? +

Aplica un stash sin eliminarlo. Parametros: index (int, default 0). It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_stash_apply? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for git_stash_apply: 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_apply? +

git_stash_apply is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit git_stash_apply? +

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

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

git_stash_apply 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 811 MCP Framework Personal tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →