High Risk →

redis_database_run_single_redis_command

Run a single Redis command

Executes arbitrary Redis operations

Part of the Upstash MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@@upstash/mcp-server Execute Risk 5/5

AI agents invoke redis_database_run_single_redis_command to trigger processes or run actions in Upstash. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

redis_database_run_single_redis_command can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

upstash.yaml
tools:
  redis_database_run_single_redis_command:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Upstash policy for all 15 tools.

Tool Name redis_database_run_single_redis_command
Category Execute
MCP Server Upstash MCP Server
Risk Level High

View all 15 tools →

Agents calling execute-class tools like redis_database_run_single_redis_command have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

redis_database_run_single_redis_command is one of the high-risk operations in Upstash. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the redis_database_run_single_redis_command tool do? +

Run a single Redis command. It is categorised as a Execute tool in the Upstash 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_database_run_single_redis_command? +

Add a rule in your Intercept YAML policy under the tools section for redis_database_run_single_redis_command. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Upstash MCP server.

What risk level is redis_database_run_single_redis_command? +

redis_database_run_single_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_database_run_single_redis_command? +

Yes. Add a rate_limit block to the redis_database_run_single_redis_command rule in your Intercept 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_database_run_single_redis_command completely? +

Set action: deny in the Intercept policy for redis_database_run_single_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_database_run_single_redis_command? +

redis_database_run_single_redis_command is provided by the Upstash MCP server (@@upstash/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Upstash

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.