scan_all_keys
AI agents call scan_all_keys to retrieve information from Redis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Scanning all keys is a retrieval operation with no side effects—it queries the keyspace but does not create, modify, or delete data. This is typical Read behavior. Severity is medium rather than low because unrestricted key scanning could expose sensitive data or cause performance issues on large Redis instances if misused by an agent.
From the tool's definition Tool name 'scan_all_keys' indicates retrieval of data keys from Redis without modification. The sibling tools include 'get', 'dbsize', and 'get_index_info' which are clearly Read operations, suggesting this tool fits the same pattern.
Attacks that exploit this kind of access
scan_all_keys. It is categorised as a Read tool in the Redis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for scan_all_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 Redis MCP Server. Nothing to install.
scan_all_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 scan_all_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 scan_all_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.
scan_all_keys is provided by the Redis MCP Server MCP server (yuchenhui/mcp-redis). 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 →