Get detailed information about a specific queue including message rates,
AI agents call rmq_queue_info 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.
This tool queries and retrieves queue information (message rates, queue details) with no capability to modify data, execute code, or trigger external operations. It is a passive read operation with minimal security impact. The incomplete description cuts off mid-sentence but the 'Get detailed information' phrasing confirms read-only behavior.
From the tool's definition Tool name 'rmq_queue_info' and description 'Get detailed information about a specific queue including message rates' indicate retrieval of queue statistics without modification or execution.
Attacks that exploit this kind of access
Get detailed information about a specific queue including message rates,. 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_queue_info: 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_queue_info 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_queue_info 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_queue_info. 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_queue_info 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 →