Close all connections for a specific username. Optionally provide a reason.
AI agents call delete-connections-username 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.
Closing all connections for a user is a destructive action that cannot be easily undone and causes immediate loss of service for that user. While not data deletion, it terminates active sessions forcibly, which constitutes an irreversible operational disruption. The tool sits alongside other destructive operations (delete-exchange, delete-binding, etc.) in the RabbitMQ server, reinforcing its destructive nature.
From the tool's definition Tool name and description: "delete-connections-username" - "Close all connections for a specific username." This terminates active connections, which is an irreversible operation that forcibly disconnects users and disrupts their sessions.
Attacks that exploit this kind of access
Close all connections for a specific username. Optionally provide a reason. 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 delete-connections-username: 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.
delete-connections-username 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 delete-connections-username 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 delete-connections-username. 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.
delete-connections-username 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.
delete-connections-username is one line of Rabbitmq's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →