Delete a field from a Redis hash.
AI agents call hdel to permanently remove resources in Redis MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a field from a Redis hash, which is an irreversible operation. While it only deletes a single field rather than an entire key or database, the destructive nature of deletion makes it more severe than Write operations. The blast radius is significant if an AI agent mistakenly deletes important hash fields, particularly in production Redis instances containing critical data.
From the tool's definition Tool name 'hdel' and description 'Delete a field from a Redis hash' indicate irreversible deletion of data. The action cannot be undone.
Attacks that exploit this kind of access
Delete a field from a Redis hash. It is categorised as a Destructive tool in the Redis MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for hdel: 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 Server. Nothing to install.
hdel 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 hdel 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 hdel. 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.
hdel is provided by the Redis MCP Server MCP server (yuchenhui/mcp-redis). 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 →