AI agents call redis_del to permanently remove resources in Db — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a Redis key is an irreversible operation — once deleted, the key and its associated data are gone unless a backup exists. This maps directly to the Destructive category. The blast radius is high because an AI agent could delete critical keys (e.g., session data, cache, configuration), potentially disrupting services.
From the tool's definition Tool name 'redis_del' and description '删除 Redis 键' (Delete Redis key) clearly indicate irreversible deletion of Redis keys.
Documented attack patterns abuse exactly the kind of access redis_del gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db, and nothing reaches the server without passing your rules. This is the rule we recommend for redis_del:
{
"version": "1",
"default": "deny",
"hide": [
"redis_del"
]
}redis_del 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.
删除 Redis 键. It is categorised as a Destructive tool in the Db MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Db MCP server in PolicyLayer and add a rule for redis_del: 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 Db. Nothing to install.
redis_del 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_del 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_del. 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_del is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db, 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.
34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.