This record as markdown: /tools/redis/delete.md
What delete does on Redis
AI agents call delete to permanently remove resources in Redis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete is rated Critical
The delete operation permanently removes keys and their associated data from Redis. This action cannot be undone and results in data loss. While severity is 'high' rather than 'critical' because impact is scoped to the Redis instance itself (not system-wide or financial), it is clearly Destructive as it irreversibly deletes data.
From the tool's definition Tool name 'delete' combined with description 'Delete one or more keys from Redis' explicitly indicates irreversible removal of data from a Redis store.
Risk signalsPermanently removes data entries
Attacks that exploit this kind of access
The rule that runs delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Redis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete, this is the rule to start with:
delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Redis, apply this rule, and every delete call is checked against it from then on.
Questions about delete
Delete one or more keys from Redis. It is categorised as a Destructive tool in the Redis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redis MCP server in PolicyLayer and add a rule for delete: 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. Nothing to install.
delete 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 delete 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 delete. 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.
delete is provided by the Redis MCP server (@@modelcontextprotocol/server-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Redis, and thousands of servers like it.
Across the catalogue