List all bindings, optionally filtered by queue or exchange.
AI agents call rmq_binding_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 retrieves RabbitMQ binding information for visibility and monitoring purposes. It performs no data modification, deletion, or external execution. While it accesses operational data, the blast radius of misuse is minimal—an AI agent querying bindings cannot cause production damage. This is a straightforward Read operation consistent with enterprise monitoring tools.
From the tool's definition Tool name is 'rmq_binding_list' and description states 'List all bindings, optionally filtered by queue or exchange.' This is a query/list operation that retrieves data without modification.
Attacks that exploit this kind of access
List all bindings, optionally filtered by queue or exchange. 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_binding_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_binding_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_binding_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_binding_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_binding_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 →