AI agents call list-bindings-exchange-queue to retrieve information from Rabbitmq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
queue | string | Yes | |
vhost | string | Yes | |
exchange | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves and displays information about existing bindings between RabbitMQ exchanges and queues. It performs no modifications, deletions, or state changes. It is a pure read operation that queries the current configuration state of the message broker, making it low-risk from a security perspective.
From the tool's definition Tool name 'list-bindings-exchange-queue' and description 'List bindings between an exchange and a queue' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List bindings between an exchange and a queue. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
list-bindings-exchange-queue accepts 3 parameters: queue, vhost, exchange. Required: queue, vhost, exchange. 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 list-bindings-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.
list-bindings-exchange-queue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-bindings-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.
Set action: deny in the PolicyLayer policy for list-bindings-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.
list-bindings-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.
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 →