redis-command
Executes a Redis command via redis-cli and returns the response.
This record as markdown: /tools/io-github-dave-london-docker/redis-command.md
What redis-command does on Docker
AI agents invoke redis-command to trigger actions in Docker. 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.
Why redis-command is rated High
The tool executes arbitrary Redis commands through redis-cli. Depending on arguments, this can read data, write/modify data, delete keys (FLUSHALL, DEL), or perform other destructive operations. Since arbitrary commands can be passed, the most severe applicable category is Execute. The blast radius is high because Redis commands can flush entire databases, modify critical data, or expose sensitive cached information.
From the tool's definition 'Executes a Redis command via redis-cli and returns the response'
Attacks that exploit this kind of access
The rule that runs redis-command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every redis-command call is checked against it from then on.
Questions about redis-command
Executes a Redis command via redis-cli and returns the response. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docker 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 Docker. Nothing to install.
redis-command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
redis-command is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
Across the catalogue