Find all keys matching a pattern
AI agents call redis_keys to retrieve information from Mcp Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs pattern matching and retrieval of key names from a Redis database. It has no side effects—it does not create, modify, delete, or execute arbitrary operations. The action is analogous to a search or list operation, which falls squarely under the Read category. The blast radius of misuse is low, as an agent could only discover data structures but not alter them.
From the tool's definition Tool name 'redis_keys' and description 'Find all keys matching a pattern' indicate a query operation that retrieves data without modification. Redis KEYS command is a read-only operation that returns matching keys from the database.
Attacks that exploit this kind of access
Find all keys matching a pattern. It is categorised as a Read tool in the Mcp Database MCP Server, which means it retrieves data without modifying state.
Register the Mcp Database MCP server in PolicyLayer and add a rule for redis_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 Mcp Database. Nothing to install.
redis_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_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_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_keys is provided by the Mcp Database MCP server (nam088/mcp-database-server). 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 →