AI agents call get-topic-permission 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 | |
vhost | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves and queries existing topic permission data for a specified user in a virtual host. It performs a read-only operation without modifying, deleting, or executing any changes to the system. No data is created, destroyed, or altered. The presence of destructive sibling tools (delete-*, bulk-delete-users) on the same server does not change the classification of this specific read operation.
From the tool's definition Tool name is 'get-topic-permission' and description states 'Get topic permissions for a user in a vhost.' The verb 'Get' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get topic permissions for a user in a vhost. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
get-topic-permission accepts 2 parameters: user, vhost. Required: user, vhost. 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 get-topic-permission: 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-topic-permission 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-topic-permission 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-topic-permission. 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-topic-permission 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 →