git_stash_apply · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_stash_apply does on Git MCP Server

AI agents use git_stash_apply to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.

WHY IT NEEDS A POLICY

Why git_stash_apply needs a policy

This tool modifies files in the working directory, placing it in the Write category rather than Read. It is not Destructive because the operation is fully reversible and the stash is preserved. Severity is medium because unintended stash application could overwrite work in progress, but this can be recovered.

From the tool's definition Tool description states it 'Apply stashed changes to the working directory,' which modifies the working directory by applying previously saved changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_stash_apply Rate-limited

git_stash_apply stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Git MCP Server, so you can run agents against it safely.

FAQ

Questions about git_stash_apply

What does the git_stash_apply tool do? +

Apply stashed changes to the working directory. Applies changes from the specified stash to the current working directory, but keeps the stash in the stash list. It is categorised as a Write tool in the Git MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_stash_apply? +

Register the Git MCP Server 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 Git MCP Server. Nothing to install.

What risk level is git_stash_apply? +

git_stash_apply is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 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.