# volume-ls

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

Agent View of the PolicyLayer registry record for `volume-ls`. HTML page: https://policylayer.com/tools/io-github-dave-london-pare-test/volume-ls

## Facts

- Tool: `volume-ls`
- Server: Test (`Dave-London/Pare`) — https://policylayer.com/tools/io-github-dave-london-pare-test.md
- Homepage: https://github.com/Dave-London/Pare
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "volume-ls",
    "arguments": {}
  }
}
```

## Why volume-ls is rated Low

This tool performs a non-destructive query of Docker volumes and returns structured metadata (driver, mountpoint, scope). It has no capability to create, modify, delete, or execute operations. The blast radius is minimal—an AI agent misusing this tool could at worst discover volume names and locations, but cannot cause irreversible harm or trigger external side effects beyond information disclosure.

From the tool's own definition: "Tool name 'volume-ls' and description 'Lists Docker volumes with structured driver, mountpoint, and scope information' indicate a read-only query operation that retrieves and returns information about existing Docker volumes."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Test:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "volume-ls": {}
  }
}
```

## Other tools on Test (201)

- `branch` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/branch.md
- `clean` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/clean.md
- `package-clean` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/package-clean.md
- `remove` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/remove.md
- `reset` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/reset.md
- `secret-delete` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/secret-delete.md
- `stash` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/stash.md
- `tag` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/tag.md
- `variable-delete` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/variable-delete.md
- `workspace` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/workspace.md
- `worktree` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-test/worktree.md
- `add` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/add.md
- `add-package` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/add-package.md
- `ansible-galaxy` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/ansible-galaxy.md
- `ansible-playbook` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/ansible-playbook.md
- `api` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/api.md
- `apply` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/apply.md
- `bazel` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/bazel.md
- `biome-check` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/biome-check.md
- `bisect` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/bisect.md
- `black` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/black.md
- `build` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/build.md
- `bundle-exec` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/bundle-exec.md
- `check` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/check.md
- `cherry-pick` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/cherry-pick.md
- `clippy` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/clippy.md
- `cmake` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/cmake.md
- `compose-build` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/compose-build.md
- `compose-down` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/compose-down.md
- `compose-up` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-test/compose-up.md
- …and 171 more: https://policylayer.com/tools/io-github-dave-london-pare-test.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-dave-london-pare-test · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-dave-london-pare-test