volume-ls
Lists Docker volumes with structured driver, mountpoint, and scope information.
This record as markdown: /tools/io-github-dave-london-http/volume-ls.md
What volume-ls does on Http
AI agents call volume-ls to retrieve information from Http without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why volume-ls is rated Low
This tool performs a simple listing/query operation on Docker volumes, returning metadata about drivers, mountpoints, and scope. It has no side effects, does not modify data, execute code, or affect system state. The blast radius of misuse is minimal—an agent could only discover information about existing volumes, not create, modify, or delete them.
From the tool's definition Tool name 'volume-ls' and description 'Lists Docker volumes' indicate a read-only operation that retrieves and displays Docker volume information without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs volume-ls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Http, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For volume-ls, this is the rule to start with:
volume-ls 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 Http, apply this rule, and every volume-ls call is checked against it from then on.
Questions about volume-ls
Lists Docker volumes with structured driver, mountpoint, and scope information. It is categorised as a Read tool in the Http MCP Server, which means it retrieves data without modifying state.
Register the Http MCP server in PolicyLayer and add a rule for volume-ls: 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 Http. Nothing to install.
volume-ls 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 volume-ls 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 volume-ls. 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.
volume-ls is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Http, and thousands of servers like it.
This server
Across the catalogue