Delete a queue entirely or purge all its messages. Requires confirmation.
AI agents call rmq_queue_delete to permanently remove resources in RedisNexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of message queue data. Even though it requires confirmation (a mitigating factor), the actual operation cannot be undone—deleted messages and queues cannot be recovered. This qualifies as Destructive rather than Write. In a production environment managing Redis/message queues, misuse could cause significant data loss and service disruption, warranting high severity.
From the tool's definition Tool description states "Delete a queue entirely or purge all its messages." The verbs 'delete' and 'purge' are irreversible operations that destroy data without recovery possibility.
Attacks that exploit this kind of access
Delete a queue entirely or purge all its messages. Requires confirmation. It is categorised as a Destructive tool in the RedisNexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RedisNexus MCP server in PolicyLayer and add a rule for rmq_queue_delete: 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 RedisNexus. Nothing to install.
rmq_queue_delete 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 rmq_queue_delete 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 rmq_queue_delete. 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.
rmq_queue_delete is provided by the RedisNexus MCP server (rajkumar-madhu/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 →