Delete key from Redis (requires FULL mode)
AI agents call redis_del to permanently remove resources in Multi-Database MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Redis DEL commands permanently delete keys and their associated values. This is an irreversible data destruction operation. While a single key deletion has a narrower blast radius than bulk destructive operations, the permanent nature and the requirement for FULL mode (indicating heightened privilege/risk awareness) classify this as Destructive rather than Write.
From the tool's definition Tool name is 'redis_del' with description 'Delete key from Redis (requires FULL mode)'. The DEL operation irreversibly removes data from Redis with no built-in undo mechanism.
Attacks that exploit this kind of access
Delete key from Redis (requires FULL mode). It is categorised as a Destructive tool in the Multi-Database MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Multi-Database MCP Server 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 Multi-Database MCP Server. 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 Multi-Database MCP Server MCP server (nam088/mcp-server). 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 →