【暂存操作】Git stash 管理。action 支持：list(列表)/save(保存)/pop(弹出)/apply(应用)/drop(丢弃)/clear(清空)。
AI agents call git_stash to permanently remove resources in LuzzyTool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool supports multiple git stash operations. While 'list', 'save', 'pop', and 'apply' are reversible or read-like operations, 'drop' and 'clear' permanently delete stashed entries which cannot be recovered. Per the rules, the most severe applicable category must be chosen, making this Destructive. Severity is medium because only stashed (uncommitted) changes are at risk, not committed history.
From the tool's definition drop(丢弃)/clear(清空) — these actions irreversibly discard stashed changes
Attacks that exploit this kind of access
【暂存操作】Git stash 管理。action 支持：list(列表)/save(保存)/pop(弹出)/apply(应用)/drop(丢弃)/clear(清空)。. It is categorised as a Destructive tool in the LuzzyTool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LuzzyTool 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 LuzzyTool. 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 LuzzyTool MCP server (luzzymeow/luzzytool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →