Delete one or more hash fields (requires FULL mode)
AI agents call redis_hdel 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.
This tool permanently removes hash fields from Redis, which is an irreversible operation. Once deleted, the data cannot be recovered through normal means. This qualifies as Destructive rather than Write (which is reversible) or Execute (which is for triggering operations with variable effects). The requirement for 'FULL mode' suggests administrative-level access.
From the tool's definition Tool name 'redis_hdel' and description 'Delete one or more hash fields' - the verb 'Delete' indicates irreversible removal of data from Redis hash structures.
Attacks that exploit this kind of access
Delete one or more hash fields (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_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 Multi-Database MCP Server. Nothing to install.
redis_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 redis_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 redis_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.
redis_hdel 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 →