Delete an entry from a Redis stream.
AI agents call xdel 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.
This tool permanently removes data from a Redis stream without possibility of recovery (unless backups exist outside the tool's control). Destructive operations are more severe than Execute or Write operations because they cannot be undone through the tool itself. In the context of an AI agent with unrestricted access, a misclassification or hallucination could result in unintended data loss from production streams.
From the tool's definition Tool name 'xdel' and description 'Delete an entry from a Redis stream' indicate irreversible deletion of data. The term 'Delete' combined with removal from a stream confirms the destructive nature of this operation.
Attacks that exploit this kind of access
Delete an entry from a Redis stream. 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.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for xdel: 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.
xdel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the xdel 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 xdel. 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.
xdel 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 →