AI agents call get-exchange-bindings-destination 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 |
|---|---|---|---|
name | string | Yes | |
vhost | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves and lists existing binding information from RabbitMQ without creating, modifying, or deleting any resources. The verb 'get' and 'list' are hallmarks of Read category operations. No data is altered, and there are no destructive or external execution effects. The blast radius is minimal—at most information disclosure about message broker topology.
From the tool's definition Tool name 'get-exchange-bindings-destination' and description 'List bindings to an exchange (destination)' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List bindings to an exchange (destination). It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
get-exchange-bindings-destination accepts 2 parameters: name, vhost. Required: name, vhost. 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 get-exchange-bindings-destination: 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.
get-exchange-bindings-destination 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 get-exchange-bindings-destination 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 get-exchange-bindings-destination. 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.
get-exchange-bindings-destination 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 →