Low Risk

volume-ls

Lists Docker volumes with structured driver, mountpoint, and scope information.

Accepts file system path (path)

Part of the Docker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/docker Read Risk 2/5

AI agents call volume-ls to retrieve information from Docker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though volume-ls only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-dave-london-docker.yaml
tools:
  volume-ls:
    rules:
      - action: allow

See the full Docker policy for all 16 tools.

Tool Name volume-ls
Category Read
MCP Server Docker MCP Server
Risk Level Low

View all 16 tools →

Agents calling read-class tools like volume-ls have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the volume-ls tool do? +

Lists Docker volumes with structured driver, mountpoint, and scope information.. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on volume-ls? +

Add a rule in your Intercept YAML policy under the tools section for volume-ls. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docker MCP server.

What risk level is volume-ls? +

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

Can I rate-limit volume-ls? +

Yes. Add a rate_limit block to the volume-ls rule in your Intercept 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 volume-ls completely? +

Set action: deny in the Intercept 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.

What MCP server provides volume-ls? +

volume-ls is provided by the Docker MCP server (@paretools/docker). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Docker

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.