AI agents invoke xreadgroup to trigger actions in Redis MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The Redis XREADGROUP command reads messages from a stream and registers them as pending for a consumer group — it has both read and state-modification side effects (it advances consumer group offsets and marks messages as pending). This makes it more than a pure Read. Without a description to confirm exact behavior, confidence is lowered.
From the tool's definition Tool name 'xreadgroup' with empty description. Based on the name, this corresponds to the Redis XREADGROUP command, which reads messages from a stream as part of a consumer group.
Documented attack patterns abuse exactly the kind of access xreadgroup 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 xreadgroup:
{
"version": "1",
"default": "deny",
"tools": {
"xreadgroup": {
"limits": [
{
"counter": "xreadgroup_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} xreadgroup stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
xreadgroup. It is categorised as a Execute tool in the Redis MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for xreadgroup: 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.
xreadgroup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the xreadgroup 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 xreadgroup. 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.
xreadgroup 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.