Remove a value from a Redis set. Args: name: The Redis set key. value: The value to remove from the set. Returns: A success message or an error message.
AI agents call srem 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.
The tool irreversibly removes a member from a Redis set. Once removed, the value is gone unless explicitly re-added. This is a destructive operation with no undo mechanism, making it more severe than a simple write. Severity is medium because it affects individual set members rather than entire datasets or indexes.
From the tool's definition Remove a value from a Redis set
Documented attack patterns abuse exactly the kind of access srem 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 srem:
{
"version": "1",
"default": "deny",
"hide": [
"srem"
]
}srem 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 a value from a Redis set. Args: name: The Redis set key. value: The value to remove from the set. Returns: A success message or an error message. 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 srem: 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.
srem 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 srem 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 srem. 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.
srem 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.