git_stash · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_stash does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why git_stash needs a policy

git_stash temporarily saves work-in-progress changes to a stack, allowing the working directory to be reverted. This is a Write operation because it creates new stash entries (reversible state changes), not a Read operation (which would only query state) and not Destructive (stashes can be popped or dropped, and the original changes remain accessible).

From the tool's definition Tool name 'git_stash' and description 'Stashes current changes' indicate this creates a temporary storage of uncommitted modifications. Stashing is a reversible operation that modifies the working directory state by storing changes without committing them.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_stash Rate-limited

git_stash 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": {
      "limits": [
        {
          "counter": "git_stash_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 GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about git_stash

What does the git_stash tool do? +

Stashes current changes. It is categorised as a Write tool in the GitHub 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? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git_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 MCP Server. Nothing to install.

What risk level is git_stash? +

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

Can I rate-limit git_stash? +

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

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

git_stash is provided by the GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.