AI agents call list-user-topic-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.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | Yes |
Parameters from the server's own tool schema.
This tool queries and retrieves topic permission data for a user without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns information about existing permissions. The low severity reflects minimal blast radius: unauthorized enumeration of permissions poses limited operational risk compared to modification or deletion of permissions or users.
From the tool's definition Tool name contains 'list' and description states 'List all topic permissions for a user' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all topic permissions for a user. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
list-user-topic-permissions accepts 1 parameter: user. Required: user. The full parameter table on this page comes from the server's own tool schema.
Register the Rabbitmq MCP server in PolicyLayer and add a rule for list-user-topic-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-user-topic-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-user-topic-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-user-topic-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-user-topic-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 →