stash-list

Lists all stash entries with index, message, date, branch, and optional file change summary. Returns structured stash data.

SERVERCargo SOURCEDave-London/Pare

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-cargo/stash-list.md

WHAT IT DOES

What stash-list does on Cargo

AI agents call stash-list to retrieve information from Cargo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why stash-list is rated Low

This tool performs a read-only operation on git stash entries. It queries and returns information about existing stashes (index, message, date, branch, file changes) but does not create, modify, or delete any data. There are no side effects beyond retrieving information. This is consistent with typical 'list' operations which are classified as Read category.

From the tool's definition Tool name 'stash-list' and description 'Lists all stash entries' indicates a query operation that retrieves stash data without modification. The description emphasizes returning structured data with no mention of creating, modifying, or deleting stash entries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stash-list 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-list, this is the rule to start with:

stash-list Allowed

stash-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stash-list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cargo, apply this rule, and every stash-list call is checked against it from then on.

FAQ

Questions about stash-list

What does the stash-list tool do? +

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 Cargo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stash-list? +

Register the Cargo 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 Cargo. Nothing to install.

What risk level is stash-list? +

stash-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stash-list? +

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.

How do I block stash-list completely? +

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.

What MCP server provides stash-list? +

stash-list 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.

KEEP EXPLORING

More on Cargo, and thousands of servers like it.

This server

All 202 Cargo tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →