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-pare-search/stash.md
What stash does on Search
AI agents call stash to permanently remove resources in Search, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why stash is rated Critical
The tool supports multiple stash operations. While push/pop/apply/show are reversible (Write/Read), 'drop' and 'clear' permanently delete stash entries with no recovery path. Per the rules, the most severe applicable category applies, making this Destructive. Severity is high because stash entries may contain significant uncommitted work that would be permanently lost.
From the tool's definition 'drops' and 'clears stash entries' — dropping or clearing stash entries irreversibly removes saved work that cannot be recovered
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 Search, 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 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 Search, 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 Destructive tool in the Search MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Search 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 Search. Nothing to install.
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 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 Search 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 Search, and thousands of servers like it.
Across the catalogue