scan_keys
AI agents call scan_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.
scan_keys is a standard Redis operation that iterates over keys without side effects. Although the tool description is empty, the name and context strongly suggest it retrieves or enumerates keys (a read operation). No data is modified, deleted, or executed. Confidence is slightly lowered due to missing description, but the semantic clarity of 'scan' and positioning alongside other introspection tools is high.
From the tool's definition Tool name 'scan_keys' indicates key enumeration/iteration without modification. Sibling tools include read-only operations (client_list, dbsize, get, get_index_info, get_indexes, get_vector_from_hash) and destructive/write operations (delete, expire,…
Attacks that exploit this kind of access
scan_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_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_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_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_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_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 →