批量删除匹配的键
AI agents call key_delete_pattern to permanently remove resources in Redis MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data from Redis, matching the Destructive category definition. The pattern-matching aspect increases severity as it could delete large volumes of data if the pattern is overly broad. While not Financial or Execute-level critical, unauthorized or mistaken use could result in significant data loss. High severity reflects the blast radius of unintended mass deletion.
From the tool's definition Tool name 'key_delete_pattern' combined with description '批量删除匹配的键' (batch delete matching keys) indicates irreversible deletion of data. The pattern-based deletion capability means multiple keys can be removed at once without recovery option.
Attacks that exploit this kind of access
批量删除匹配的键. It is categorised as a Destructive tool in the Redis MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redis MCP server in PolicyLayer and add a rule for key_delete_pattern: 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 MCP. Nothing to install.
key_delete_pattern 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 key_delete_pattern 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 key_delete_pattern. 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.
key_delete_pattern is provided by the Redis MCP server (pickstar-2002/redis-mcp). 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 →