Delete topic permissions for a user in a vhost.
AI agents call delete-topic-permission to permanently remove resources in Rabbitmq — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | Yes | |
vhost | string | Yes |
Parameters from the server's own tool schema.
This tool permanently deletes access permissions, which cannot be easily undone and represents an irreversible change to system authorization state. While not data destruction, permission deletion is a destructive authorization operation. The high severity reflects that an AI agent misusing this could lock users out of critical message queue topics, disrupting application messaging and user workflows.
From the tool's definition Tool name contains 'delete' and description states 'Delete topic permissions for a user in a vhost.' The action irreversibly removes access controls.
Attacks that exploit this kind of access
Delete topic permissions for a user in a vhost. It is categorised as a Destructive tool in the Rabbitmq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete-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 delete-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.
delete-topic-permission is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-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 delete-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.
delete-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 →