AI agents call list-users-without-permissions 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 and returns information about users lacking permissions in RabbitMQ. It performs no writes, deletions, executions, or financial operations. The read-only nature and limited scope (informational query) result in low severity, as misuse would only expose existing data rather than cause operational damage or unauthorized state changes.
From the tool's definition Tool name 'list-users-without-permissions' and description 'List all users without permissions' indicate a query/retrieval operation with no modification or execution of commands.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all users without permissions. 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 list-users-without-permissions: 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.
list-users-without-permissions 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 list-users-without-permissions 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 list-users-without-permissions. 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.
list-users-without-permissions 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 →