Delete a key from Redis.
AI agents call redis_delete to permanently remove resources in Redshift MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of keys from Redis is a destructive action that permanently removes data. While the blast radius depends on what data is stored and how critical it is to the application, any unintended deletion could cause data loss. This is categorized as Destructive rather than Write because the operation is not reversible.
From the tool's definition Tool description states 'Delete a key from Redis' — deletion is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete a key from Redis. It is categorised as a Destructive tool in the Redshift MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redshift MCP Server 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 Redshift MCP Server. 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 Redshift MCP Server MCP server (santosh07401/redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
redis_delete is one line of Redshift MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →