volume-ls

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

SERVERGit 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-git/volume-ls.md

WHAT IT DOES

What volume-ls does on Git

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

RISK

Why volume-ls is rated Low

The tool retrieves and presents information about existing Docker volumes without side effects. It is purely informational (read-only), making it a Read category risk. Severity is low because exposing volume metadata poses minimal security risk compared to tools that could modify or delete infrastructure.

From the tool's definition Tool name and description indicate listing/querying Docker volumes: 'Lists Docker volumes with structured driver, mountpoint, and scope information.' No modification, deletion, or execution of commands occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs volume-ls safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, 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 Allowed

volume-ls 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": {
    "volume-ls": {}
  }
}

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

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

FAQ

Questions about volume-ls

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

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

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

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 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 volume-ls completely? +

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.

What MCP server provides volume-ls? +

volume-ls is provided by the Git 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 Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

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