This record as markdown: /tools/io-github-kivanccakmak-yaver/git-stash.md
What git_stash does on Yaver
AI agents call git_stash to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | list, save, pop, apply, drop |
message | string | — |
Parameters from the server's own tool schema.
Why git_stash is rated Critical
The tool includes 'drop' which irreversibly deletes a stash, and 'pop' which removes a stash after applying it. These operations cannot be undone. While some sub-operations (list, save, apply) are reversible, the most severe applicable category is Destructive due to 'drop' and 'pop' capabilities.
From the tool's definition Manage git stashes (list, save, pop, apply, drop)
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 Yaver, 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 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_stash call is checked against it from then on.
Questions about git_stash
Manage git stashes (list, save, pop, apply, drop). It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
git_stash accepts 2 parameters: action, message. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. Nothing to install.
git_stash is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue