Retrieve the number of indexed keys by the index
AI agents call get_indexed_keys_number 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.
This tool performs a read-only query to return a count of indexed keys. It has no side effects, does not modify, delete, or execute code. It falls clearly into the Read category as a data retrieval operation. Severity is low because misconfiguration would only expose non-sensitive metadata about indexing.
From the tool's definition Tool name 'get_indexed_keys_number' and description 'Retrieve the number of indexed keys by the index' indicate a query operation that retrieves metadata/statistics about an index without modifying any data.
Attacks that exploit this kind of access
Retrieve the number of indexed keys by the index. 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 get_indexed_keys_number: 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.
get_indexed_keys_number 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 get_indexed_keys_number 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 get_indexed_keys_number. 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.
get_indexed_keys_number 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 →