git_stash

Stash working-tree changes (git stash push).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/git-stash.md

WHAT IT DOES

What git_stash does on LocalAnt

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

RISK

Why git_stash is rated Medium

git stash push saves uncommitted working-tree changes to a stash stack, which is a reversible write operation. Changes are not deleted — they can be recovered via git stash pop/apply. However, misuse could cause confusion or loss of context if stash entries are not managed properly. Not destructive since the operation is reversible.

From the tool's definition Stash working-tree changes (git stash push)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_stash safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, 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:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every git_stash call is checked against it from then on.

FAQ

Questions about git_stash

What does the git_stash tool do? +

Stash working-tree changes (git stash push). It is categorised as a Write tool in the LocalAnt 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 LocalAnt 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 LocalAnt. 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 LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →