# set

Set a Redis key-value pair

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

## Facts

- Tool: `set`
- 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: Write (Medium risk)
- Registry record: grade F, identity verified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why set is rated Medium

This tool modifies data (creates or updates key-value pairs) but the operation is reversible. It does not execute arbitrary code, delete data irreversibly, or move money. Among sibling tools (delete, get, list), SET is a write operation with medium severity due to potential for data modification in a datastore.

From the tool's own definition: "Tool name 'set' with description 'Set a Redis key-value pair' indicates creation or modification of data. Redis SET command creates or overwrites keys, which is reversible through subsequent SET or DEL commands."

Risk signals: Writes data to Redis

## Use case

AI agents use set to create or update resources in Redis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redis environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set": {
      "limits": [
        {
          "counter": "set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Redis (3)

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