// SCAN REPORT

Redis CRUD MCP Server

9 tools. 4 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 4 Jul 2026

4 can modify or destroy data

5 read-only

9 tools total

Community server · catalogue entry verified 04/07/2026

How to control Redis CRUD MCP Server ↓

TOOL MAP

What Redis CRUD MCP Server exposes to your agents

Read (5) Write / Execute (2) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Redis CRUD MCP Server tools

Destructive · High redis_del Deleting a Redis key is an irreversible operation — once deleted, the key and its associated data are gone unless a backup exists. Destructive · High redis_hdel This tool deletes fields from a Redis hash, which is an irreversible destructive operation. Write · Medium redis_hset redis_hset modifies data in Redis by setting a field within a hash data structure. Write · Medium redis_set redis_set creates or modifies key-value pairs in Redis.

4 of Redis CRUD MCP Server's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Redis CRUD MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Redis CRUD MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "redis_del": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "redis_hset": {
    "limits": [
      {
        "counter": "redis_hset_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "redis_exists": {
    "limits": [
      {
        "counter": "redis_exists_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Redis CRUD MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REDIS CRUD →

Instant setup, no code required.

FULL CATALOGUE

All 9 Redis CRUD MCP Server tools

DESTRUCTIVE 2 tools

Destructive redis_del 删除键。 Destructive redis_hdel 删除哈希字段。

WRITE 2 tools

Write redis_hset 设置哈希字段。 Write redis_set 设置键值。自动读取项目 .env 配置连接 Redis。

READ 5 tools

Read redis_exists 检查键是否存在。 Read redis_get 获取键值。 Read redis_hget 获取哈希字段。 Read redis_hgetall 获取哈希所有字段。 Read redis_info 获取连接信息。

FAQ

Questions about Redis CRUD MCP Server

Can an AI agent delete data through the Redis CRUD MCP Server MCP server? +

Yes. The Redis CRUD MCP Server server exposes 2 destructive tools including redis_del, redis_hdel. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Redis CRUD MCP Server? +

The Redis CRUD MCP Server server has 2 write tools including redis_hset, redis_set. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Redis CRUD MCP Server.

How many tools does the Redis CRUD MCP Server MCP server expose? +

9 tools across 2 categories: Read, Write. 5 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Redis CRUD MCP Server? +

Register the Redis CRUD MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Redis CRUD MCP Server tool call.

Deterministic rules across all 9 Redis CRUD MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REDIS CRUD →

Instant setup, no code required.

9 Redis CRUD MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.