AI agents call delete_key to permanently remove resources in MCP Server Redis — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from Redis without a reversible operation. Deletion cannot be undone without external backups. While the blast radius is limited to a single key at a time (rather than bulk operations), accidental or malicious use could remove critical cached data, session information, or application state.
From the tool's definition Tool name is 'delete_key' and description states 'Delete a Redis key'. The term 'Delete' indicates irreversible removal of data from the Redis database.
Documented attack patterns abuse exactly the kind of access delete_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Redis, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_key:
{
"version": "1",
"default": "deny",
"hide": [
"delete_key"
]
}delete_key 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.
Delete a Redis key. It is categorised as a Destructive tool in the MCP Server Redis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Server Redis MCP server in PolicyLayer and add a rule for delete_key: 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 MCP Server Redis. Nothing to install.
delete_key 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_key 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_key. 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_key is provided by the MCP Server Redis MCP server (prajwalnayak7/mcp-server-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server Redis, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Server Redis tools catalogued and risk-classified — across an index of 43,000+ MCP servers.