AI agents use stash_save 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.
The stash_save operation writes data (uncommitted changes) to Git's stash, which is a reversible action. It does not execute arbitrary code, delete data permanently, or cause financial impact. While it modifies the repository state, the changes can be recovered via stash_pop or stash_apply, making it a Write-category risk rather than Destructive.
From the tool's definition Tool name 'stash_save' and description 'Save changes to stash' indicate the tool creates/stores a reversible snapshot of uncommitted changes in Git's stash storage.
Documented attack patterns abuse exactly the kind of access stash_save gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stash_save:
{
"version": "1",
"default": "deny",
"tools": {
"stash_save": {
"limits": [
{
"counter": "stash_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}stash_save 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.
Free to start. No card required.
Save changes to stash. 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.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for stash_save: 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.
stash_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the stash_save 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.
Set action: deny in the PolicyLayer policy for stash_save. 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.
stash_save is provided by the Git MCP Server MCP server (sheshiyer/git-mcp-v2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Git MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.