delete-binding-exchange-queue · Rabbitmq MCP: Risk & Policy

WHAT IT DOES

What delete-binding-exchange-queue does on Rabbitmq

AI agents call delete-binding-exchange-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.

PARAMETERS

Parameter	Type	Required
`props`	string	Yes
`queue`	string	Yes
`vhost`	string	Yes
`exchange`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why delete-binding-exchange-queue needs a policy

This tool permanently removes message routing configuration. While not data deletion per se, bindings are critical infrastructure components whose removal is irreversible and would disrupt message flow. An AI agent misusing this could break message routing, causing operational outages.

From the tool's definition Tool name includes 'delete' and description states 'Delete a binding from an exchange to a queue' — this operation removes a configuration that routes messages between RabbitMQ components, which cannot be easily restored.

Attacks that exploit this kind of access

Questions about delete-binding-exchange-queue

What does the delete-binding-exchange-queue tool do? +

Delete a binding from an exchange to 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.

What parameters does delete-binding-exchange-queue accept? +

delete-binding-exchange-queue accepts 4 parameters: props, queue, vhost, exchange. Required: props, queue, vhost, exchange. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete-binding-exchange-queue? +

Register the Rabbitmq MCP server in PolicyLayer and add a rule for delete-binding-exchange-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.

What risk level is delete-binding-exchange-queue? +

delete-binding-exchange-queue is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-binding-exchange-queue? +

Yes. Add a rate_limit block to the delete-binding-exchange-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.

How do I block delete-binding-exchange-queue completely? +

Set action: deny in the PolicyLayer policy for delete-binding-exchange-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.

What MCP server provides delete-binding-exchange-queue? +

delete-binding-exchange-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.