AI agents call get-queue 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.
This tool retrieves queue metadata/details from RabbitMQ without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on message broker state, posing minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get-queue' and description 'Get details for a specific queue' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details for a specific queue. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
Register the Rabbitmq MCP server in PolicyLayer and add a rule for get-queue: 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-queue 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-queue 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-queue. 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-queue 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 →