# get

Get value by key from Redis

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

## Facts

- Tool: `get`
- 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": "get",
    "arguments": {}
  }
}
```

## Why get is rated Low

This tool retrieves data from Redis by key lookup. It is a read-only operation with no side effects, no data modification, and no execution of arbitrary commands. The low severity reflects that while information disclosure could occur if sensitive data is cached, the tool itself performs only safe retrieval. Confidence is high due to clear naming and description.

From the tool's own definition: "Tool name 'get' and description 'Get value by key from Redis' explicitly indicate retrieval without modification."

## Use case

AI agents call get 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": {
    "get": {}
  }
}
```

## Other tools on Redis (3)

- `delete` — Destructive — https://policylayer.com/tools/redis/delete.md
- `list` — Read — https://policylayer.com/tools/redis/list.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