stash-list
Lists all stash entries with index, message, date, branch, and optional file change summary. Returns structured stash data.
This record as markdown: /tools/io-github-dave-london-build/stash-list.md
What stash-list does on Build
AI agents call stash-list to retrieve information from Build without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stash-list is rated Low
This tool only retrieves and presents information about stashed changes (index, message, date, branch, file summaries). It performs no modifications, deletions, or side effects. The verb 'lists' confirms it is a pure read operation with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'stash-list' and description 'Lists all stash entries' clearly indicates a read-only query operation that retrieves and displays stash data without modification.
Attacks that exploit this kind of access
The rule that runs stash-list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stash-list, this is the rule to start with:
stash-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every stash-list call is checked against it from then on.
Questions about stash-list
Lists all stash entries with index, message, date, branch, and optional file change summary. Returns structured stash data. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.
Register the Build MCP server in PolicyLayer and add a rule for stash-list: 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 Build. Nothing to install.
stash-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stash-list 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-list. 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-list is provided by the Build 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 Build, and thousands of servers like it.
This server
Across the catalogue