删除键。
AI agents call redis_del to permanently remove resources in Redis CRUD MCP Server — 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 matches the Destructive category. Severity is high because a misused delete operation could wipe critical data across any supported Redis data type (strings, lists, sets, hashes, sorted sets).
From the tool's definition Tool name 'redis_del' and description '删除键' (meaning 'delete key' in Chinese) clearly indicate irreversible deletion of Redis keys.
Attacks that exploit this kind of access
删除键。. It is categorised as a Destructive tool in the Redis CRUD MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redis CRUD 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 Redis CRUD 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 Redis CRUD MCP Server MCP server (nicolas-one/redis-crud-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 →