redis_hset · Multi-Database MCP Server MCP: Risk & Policy

WHAT IT DOES

What redis_hset does on Multi-Database MCP Server

AI agents use redis_hset to create or update resources in Multi-Database MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multi-Database MCP Server environment.

WHY IT NEEDS A POLICY

Why redis_hset needs a policy

Redis HSET commands create or update hash field values, which is a reversible write operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). The 'FULL mode' requirement suggests the server has configurable permissions, but this is a standard write operation.

From the tool's definition Tool description states 'Set the value of a hash field' - a write operation that modifies data in Redis. The phrase 'requires FULL mode' indicates permission controls exist but the tool inherently performs data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

redis_hset Rate-limited

redis_hset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "redis_hset": {
      "limits": [
        {
          "counter": "redis_hset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Multi-Database MCP Server, so you can run agents against it safely.

FAQ

Questions about redis_hset

What does the redis_hset tool do? +

Set the value of a hash field (requires FULL mode). It is categorised as a Write tool in the Multi-Database MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on redis_hset? +

Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for redis_hset: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Multi-Database MCP Server. Nothing to install.

What risk level is redis_hset? +

redis_hset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit redis_hset? +

Yes. Add a rate_limit block to the redis_hset rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block redis_hset completely? +

Set action: deny in the PolicyLayer policy for redis_hset. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides redis_hset? +

redis_hset is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.