Critical Risk →

rpop

Remove and return the last element from a Redis list.

How to control rpop ↓

AI agents call rpop 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 tool irreversibly removes an element from a Redis list. Once popped, the element is gone from the list and cannot be recovered unless the application re-inserts it. This is a destructive mutation of persistent data, not merely a write/update.

From the tool's definition Remove and return the last element from a Redis list

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

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

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

Remove and return the last 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 rpop? +

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

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

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

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

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