Critical Risk →

xgroup_destroy

Destroy a consumer group for a Redis stream. Args: key (str): The stream key. group_name (str): The consumer group name. Returns: str: Confirmation message or an error message.

How to control xgroup_destroy ↓

AI agents call xgroup_destroy to permanently remove resources in Redis MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The xgroup_destroy tool permanently removes a consumer group from a Redis stream, which cannot be undone. This is a destructive operation that eliminates data structures and any associated state (pending entry lists, consumer tracking). While not deleting the stream itself, destroying a consumer group is irreversible and could disrupt applications relying on that group for message consumption and coordination.

From the tool's definition Tool name 'xgroup_destroy' and description 'Destroy a consumer group for a Redis stream' indicate irreversible deletion of a consumer group resource.

Documented attack patterns abuse exactly the kind of access xgroup_destroy 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 xgroup_destroy:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "xgroup_destroy"
  ]
}

xgroup_destroy disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Redis MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the xgroup_destroy tool do? +

Destroy a consumer group for a Redis stream. Args: key (str): The stream key. group_name (str): The consumer group name. Returns: str: Confirmation message or an error message. It is categorised as a Destructive tool in the Redis MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on xgroup_destroy? +

Register the Redis MCP Server MCP server in PolicyLayer and add a rule for xgroup_destroy: 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.

What risk level is xgroup_destroy? +

xgroup_destroy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit xgroup_destroy? +

Yes. Add a rate_limit block to the xgroup_destroy 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.

How do I block xgroup_destroy completely? +

Set action: deny in the PolicyLayer policy for xgroup_destroy. 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.

What MCP server provides xgroup_destroy? +

xgroup_destroy 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.

Enforce policy on every Redis MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.