List all exchanges with type, durability, and binding count.
AI agents call rmq_exchange_list to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation that retrieves metadata about RabbitMQ exchanges. It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an attacker gains visibility into exchange configuration but cannot alter, delete, or cause financial harm through this tool alone.
From the tool's definition Tool name contains 'list' and description states 'List all exchanges with type, durability, and binding count' - this is a query operation that retrieves information without modifying state.
Attacks that exploit this kind of access
List all exchanges with type, durability, and binding count. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for rmq_exchange_list: 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 RedisNexus. Nothing to install.
rmq_exchange_list 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 rmq_exchange_list 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 rmq_exchange_list. 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.
rmq_exchange_list is provided by the RedisNexus MCP server (rajkumar-madhu/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 →