git_stash

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 git_stash is rated Medium

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.

The rule that runs git_stash safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_stash": {
      "limits": [
        {
          "counter": "git_stash_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about git_stash