Retrieve the number of indexed keys by the index Args: index_name (str): The name of the index to retrieve information about. Returns: str: Number of indexed keys as a string
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 retrieves metadata about an index (the count of indexed keys) without creating, modifying, deleting, or executing any operations. It is a simple informational query with no side effects, falling squarely into the Read category with low severity since it only exposes statistical information about the Redis index.
From the tool's definition Tool name 'get_indexed_keys_number' and description 'Retrieve the number of indexed keys by the index' indicate a read-only query operation that returns information without modifying data.
Documented attack patterns abuse exactly the kind of access get_indexed_keys_number gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redis MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_indexed_keys_number:
{
"version": "1",
"default": "deny",
"tools": {
"get_indexed_keys_number": {}
}
}get_indexed_keys_number is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the number of indexed keys by the index Args: index_name (str): The name of the index to retrieve information about. Returns: str: Number of indexed keys as a string. 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 (redis/mcp-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 53 Redis MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
53 Redis MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.