AI agents call get-exchange 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 returns information about a RabbitMQ exchange without creating, modifying, or deleting any data. It is a straightforward query operation consistent with the Read category. The severity is low because information disclosure about exchange configuration poses minimal risk compared to tools that modify or delete resources.
From the tool's definition Tool name 'get-exchange' and description 'Get details for a specific exchange' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details for a specific exchange. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
get-exchange 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: 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 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 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. 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 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 →