# list

List Redis keys matching a pattern

Agent View of the PolicyLayer registry record for `list`. HTML page: https://policylayer.com/tools/redis/list

## Facts

- Tool: `list`
- Server: Redis (`@@modelcontextprotocol/server-redis`) — https://policylayer.com/tools/redis.md
- Install: `npx -y @@modelcontextprotocol/server-redis`
- Homepage: https://www.npmjs.com/package/@@modelcontextprotocol/server-redis
- Risk category: Read (Low risk)
- Registry record: grade F, identity verified
- 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": "list",
    "arguments": {}
  }
}
```

## Why list is rated Low

The 'list' operation queries and returns Redis keys matching a pattern. This is a read-only operation with no side effects—it does not create, modify, delete, execute code, or move money. The presence of sibling tools (delete, get, set) confirms this server offers multiple operation types, but this tool specifically performs data retrieval only.

From the tool's own definition: "Tool name 'list' with description 'List Redis keys matching a pattern' indicates a query operation that retrieves information about keys without modifying data."

## Use case

AI agents call list to retrieve information from Redis 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 Redis:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list": {}
  }
}
```

## Other tools on Redis (3)

- `delete` — Destructive — https://policylayer.com/tools/redis/delete.md
- `get` — Read — https://policylayer.com/tools/redis/get.md
- `set` — Write — https://policylayer.com/tools/redis/set.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=redis · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/redis