stash
Pushes, pops, applies, drops, shows, or clears stash entries. Returns structured result with action, success, message, and stash reference.
This record as markdown: /tools/io-github-dave-london-cargo/stash.md
What stash does on Cargo
AI agents invoke stash to trigger actions in Cargo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why stash is rated High
The stash tool triggers git stash operations (push, pop, apply, drop, clear) which are external operations with side effects on the working tree and stash stack. 'Drop' and 'clear' can be considered partially destructive (removing stash entries), but the primary nature is executing git operations.
From the tool's definition Pushes, pops, applies, drops, shows, or clears stash entries
Attacks that exploit this kind of access
The rule that runs stash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stash, this is the rule to start with:
stash stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cargo, apply this rule, and every stash call is checked against it from then on.
Questions about stash
Pushes, pops, applies, drops, shows, or clears stash entries. Returns structured result with action, success, message, and stash reference. It is categorised as a Execute tool in the Cargo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cargo MCP server in PolicyLayer and add a rule for 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 Cargo. Nothing to install.
stash is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
stash is provided by the Cargo MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cargo, and thousands of servers like it.
Across the catalogue