Delete permissions for a user in a vhost.
AI agents call delete-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 irreversibly deletes permissions, which cannot be easily undone and impacts system access control. While not a data deletion in the traditional sense, permission removal is a destructive authorization action with potential to lock users out of resources. The blast radius is high: misuse could disable legitimate user access or enable privilege escalation scenarios.
From the tool's definition Tool name contains 'delete' and description states 'Delete permissions for a user in a vhost.' The action irreversibly removes access control settings.
Attacks that exploit this kind of access
Delete 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-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-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-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-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-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-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 →