Read entries from a Redis stream. Args: key (str): The stream key. count (int, optional): Number of entries to retrieve. Returns: str: The retrieved stream entries or an error message.
AI agents call xrange 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 stream data from Redis without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects, matching the Read category definition of 'retrieves or queries data; no side effects.' Severity is low as misuse would only expose existing data without enabling harmful state changes.
From the tool's definition Tool name 'xrange' and description 'Read entries from a Redis stream' explicitly indicate data retrieval with no modification capability. Arguments are key and optional count for pagination—standard read-only access patterns.
Documented attack patterns abuse exactly the kind of access xrange 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 xrange:
{
"version": "1",
"default": "deny",
"tools": {
"xrange": {}
}
}xrange 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.
Read entries from a Redis stream. Args: key (str): The stream key. count (int, optional): Number of entries to retrieve. Returns: str: The retrieved stream entries or an error message. 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 xrange: 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.
xrange 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 xrange 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 xrange. 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.
xrange 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.