Safely scan Redis keys matching a pattern using SCAN (not KEYS).
AI agents call redis_scan_keys to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Redis keys based on a pattern. The SCAN command is a read-only operation that iterates over the keyspace without blocking or modifying data. No data is created, modified, deleted, or executed. The explicit mention of using SCAN rather than KEYS indicates a safe, cursor-based iteration approach designed for production systems. This is a classic Read operation with minimal risk.
From the tool's definition Tool description states 'scan Redis keys matching a pattern' and explicitly uses SCAN (not KEYS), which is a non-blocking, read-only operation that returns keys without side effects.
Attacks that exploit this kind of access
Safely scan Redis keys matching a pattern using SCAN (not KEYS). It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for redis_scan_keys: 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 RedisNexus. Nothing to install.
redis_scan_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the redis_scan_keys 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_scan_keys. 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_scan_keys is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →