Delete one or more Redis keys. Requires explicit confirmation (confirm=True).
AI agents call redis_delete to permanently remove resources in RedisNexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting Redis keys destroys data permanently with no recovery mechanism. Although the tool requires explicit confirmation (confirm=True), this is a mitigating control rather than a category change. The fundamental operation is destructive. In a production cache system, deleting wrong keys could cause service degradation, data loss, or downstream application failures.
From the tool's definition Tool name 'redis_delete' and description states it 'Delete[s] one or more Redis keys,' which is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete one or more Redis keys. Requires explicit confirmation (confirm=True). It is categorised as a Destructive tool in the RedisNexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RedisNexus MCP server in PolicyLayer and add a rule for redis_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 RedisNexus. Nothing to install.
redis_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 redis_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 redis_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.
redis_delete is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →