Remove elements from a Redis list. Args: name: The name of the list count: Number of elements to remove (0 = all, positive = from head, negative = from tail) element: The element value to remove Returns: A string indicating the number of elements removed.
AI agents call lrem 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 irreversibly removes elements from a Redis list. With count=0, it can remove ALL matching elements at once. Redis list operations are not transactional or recoverable by default, making this a destructive action with potentially wide blast radius if misused by an agent.
From the tool's definition Remove elements from a Redis list... count: Number of elements to remove (0 = all, positive = from head, negative = from tail)
Documented attack patterns abuse exactly the kind of access lrem 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 lrem:
{
"version": "1",
"default": "deny",
"hide": [
"lrem"
]
}lrem disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove elements from a Redis list. Args: name: The name of the list count: Number of elements to remove (0 = all, positive = from head, negative = from tail) element: The element value to remove Returns: A string indicating the number of elements removed. 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 lrem: 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.
lrem 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 lrem 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 lrem. 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.
lrem 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.