List all keys matching a pattern.
AI agents call redis_keys to retrieve information from Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The redis_keys tool retrieves and enumerates data (keys matching a pattern) without modifying or deleting anything, placing it in the Read category. Severity is medium rather than low because Redis may contain sensitive session data, credentials, or application state; an agent that lists keys could infer system structure or sensitive information.
From the tool's definition Tool name 'redis_keys' and description 'List all keys matching a pattern' indicate a query/listing operation with no modification.
Attacks that exploit this kind of access
List all keys matching a pattern. It is categorised as a Read tool in the Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redshift MCP Server 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 Redshift MCP Server. 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 Redshift MCP Server MCP server (santosh07401/redshift-mcp-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 →