git_stash
Guarda cambios temporales en stash. Parametros: message (string opcional).
This record as markdown: /tools/inggerman-mcps/git-stash.md
What git_stash does on MCP Framework Personal
AI agents use git_stash to create or update resources in MCP Framework Personal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Framework Personal environment.
Why git_stash is rated Medium
git stash saves uncommitted changes temporarily without deleting them; it is reversible via 'git stash pop' or 'git stash apply', making it a Write operation. Misuse could cause confusion or loss of context but changes are recoverable.
From the tool's definition 'Guarda cambios temporales en stash' (Saves temporary changes in stash)
Attacks that exploit this kind of access
The rule that runs git_stash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every git_stash call is checked against it from then on.
Questions about git_stash
Guarda cambios temporales en stash. Parametros: message (string opcional). It is categorised as a Write tool in the MCP Framework Personal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Framework Personal 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 MCP Framework Personal. Nothing to install.
git_stash 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 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.
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.
git_stash is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue