git_stash_create · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_stash_create does on Git MCP Server

AI agents use git_stash_create 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_create needs a policy

git_stash_create creates new data (a stash) in the repository's stash stack. While stashes are theoretically recoverable and the action is reversible (can be popped or dropped), the tool modifies repository state by adding a new object. It is not a pure Read operation (no data retrieval or query), and it does not Execute arbitrary code, trigger external processes, or Destructively delete data.

From the tool's definition The tool description states it 'Save[s] uncommitted changes to a stash' and 'Captures the current state of working directory and index and saves it on a stack of stashes.' This is a data modification operation that creates a new stash object with persistent…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_stash_create Rate-limited

git_stash_create 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_create": {
      "limits": [
        {
          "counter": "git_stash_create_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_create

What does the git_stash_create tool do? +

Save uncommitted changes to a stash. Captures the current state of working directory and index and saves it on a stack of stashes, allowing you to switch branches without committing in-progress work. 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_create? +

Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_stash_create: 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_create? +

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

Can I rate-limit git_stash_create? +

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

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

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