Purge a queue
AI agents call purge-queue to permanently remove resources in Rabbitmq — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Purging a queue removes all enqueued messages permanently and cannot be undone. This is a destructive operation that causes data loss. While it does not delete the queue itself, it destroys the queue's contents, making it more severe than Write operations.
From the tool's definition Tool name is 'purge-queue' with description 'Purge a queue'. The verb 'purge' in message queue contexts irreversibly deletes all messages from a queue without possibility of recovery.
Attacks that exploit this kind of access
Purge a queue. It is categorised as a Destructive tool in the Rabbitmq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rabbitmq MCP server in PolicyLayer and add a rule for purge-queue: 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 Rabbitmq. Nothing to install.
purge-queue 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 purge-queue 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 purge-queue. 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.
purge-queue is provided by the Rabbitmq MCP server (rabbitmq-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 →