Delete a vhost limit for a vhost.
AI agents call delete-vhost-limit 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.
This tool irreversibly deletes a vhost limit configuration. While not as severe as deleting the entire vhost or data, removing resource limits is a destructive action that cannot be undone without manual reconfiguration. The tool falls under Destructive rather than Write because deletion is permanent and requires deliberate restoration rather than simple reversal.
From the tool's definition Tool name contains 'delete' and description states 'Delete a vhost limit'. The action removes a configuration that cannot be easily restored, affecting RabbitMQ virtual host resource constraints.
Attacks that exploit this kind of access
Delete a vhost limit for 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.
Register the Rabbitmq MCP server in PolicyLayer and add a rule for delete-vhost-limit: 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-vhost-limit 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-vhost-limit 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-vhost-limit. 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-vhost-limit 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 →