Delete a binding from one exchange to another.
AI agents call delete-binding-exchange-exchange 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
props | string | Yes | |
vhost | string | Yes | |
source | string | Yes | |
destination | string | Yes |
Parameters from the server's own tool schema.
The tool performs an irreversible deletion operation. While not data destruction at the message level, deleting exchange bindings permanently removes routing configuration that cannot be trivially restored, affecting message flow topology. This qualifies as Destructive rather than Write (which is reversible) or Execute (which has variable effects).
From the tool's definition Tool name contains 'delete' and description states 'Delete a binding from one exchange to another' — this irreversibly removes the routing relationship between exchanges in RabbitMQ.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
Delete a binding from one exchange to another. 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.
delete-binding-exchange-exchange accepts 4 parameters: props, vhost, source, destination. Required: props, vhost, source, destination. The full parameter table on this page comes from the server's own tool schema.
Register the Rabbitmq MCP server in PolicyLayer and add a rule for delete-binding-exchange-exchange: 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-binding-exchange-exchange 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-binding-exchange-exchange 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-binding-exchange-exchange. 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-binding-exchange-exchange 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 →