Remove a member from a Redis sorted set.
AI agents call zrem 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.
zrem permanently removes a member from a Redis sorted set. There is no undo operation in Redis for this action; once removed, the data is gone unless separately backed up. This qualifies as Destructive. Severity is high because an AI agent could misuse this to remove arbitrary members from critical sorted sets (e.g., leaderboards, priority queues, scheduled job sets), causing irreversible data loss.
From the tool's definition "Remove a member from a Redis sorted set" — this is an irreversible deletion of data from a sorted set.
Attacks that exploit this kind of access
Remove a member from a Redis sorted set. 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 zrem: 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.
zrem 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 zrem 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 zrem. 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.
zrem 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 →