Critical Risk →

lpop

Remove and return the first element from a Redis list.

How to control lpop ↓

AI agents call lpop 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 lpop operation permanently removes an element from a list, making this a destructive action that cannot be undone without external recovery mechanisms. While it returns the value before removal, the primary effect is irreversible data deletion. This is more severe than Write (which is reversible) and qualifies as Destructive.

From the tool's definition Tool description states 'Remove and return the first element from a Redis list.' The verb 'Remove' indicates irreversible deletion of data from a Redis list structure.

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

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

lpop 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 lpop tool do? +

Remove and return the first element from a Redis list. 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 lpop? +

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

lpop 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 lpop? +

Yes. Add a rate_limit block to the lpop 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 lpop completely? +

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

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