redis-command

Executes a Redis command via redis-cli and returns the response.

SERVERTest SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-pare-test/redis-command.md

WHAT IT DOES

What redis-command does on Test

AI agents invoke redis-command to trigger actions in Test. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why redis-command is rated High

This tool runs arbitrary Redis commands via redis-cli. Depending on the command provided, it can read data, write/modify data, delete keys (DEL, FLUSHDB, FLUSHALL), or execute server-side scripts (EVAL). Since it allows arbitrary Redis commands, the most severe applicable category is Execute, with high severity due to the potential for destructive operations like FLUSHALL or data exfiltration.

From the tool's definition 'Executes a Redis command via redis-cli and returns the response'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs redis-command safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For redis-command, this is the rule to start with:

redis-command Rate-limited

redis-command stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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-command": {
      "limits": [
        {
          "counter": "redis-command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every redis-command call is checked against it from then on.

FAQ

Questions about redis-command

What does the redis-command tool do? +

Executes a Redis command via redis-cli and returns the response. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on redis-command? +

Register the Test MCP server in PolicyLayer and add a rule for redis-command: 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 Test. Nothing to install.

What risk level is redis-command? +

redis-command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit redis-command? +

Yes. Add a rate_limit block to the redis-command 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-command completely? +

Set action: deny in the PolicyLayer policy for redis-command. 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-command? +

redis-command is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Test, and thousands of servers like it.

This server

All 202 Test tools → High-risk tools on this server →

Across the catalogue

adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →