AI agents use put-operator-policy to create or update resources in Rabbitmq — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rabbitmq environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
vhost | string | Yes | |
pattern | string | Yes | |
apply_to | string | — | |
priority | number | — | |
definition | object | Yes |
Parameters from the server's own tool schema.
The tool creates or updates operator policies, which are configuration changes that are reversible. This is a Write operation (create/update) rather than Execute because it modifies policy metadata rather than triggering dynamic operations. Severity is medium because incorrect operator policies could impact message routing or access control across a vhost, but the changes are non-destructive and can be corrected.
From the tool's definition Tool name 'put-operator-policy' and description 'Create or update an operator policy for a vhost' indicate creation or modification of policy configuration.
Attacks that exploit this kind of access
Create or update an operator policy for a vhost. It is categorised as a Write tool in the Rabbitmq MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
put-operator-policy accepts 6 parameters: name, vhost, pattern, apply_to, priority, definition. Required: name, vhost, pattern, definition. 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 put-operator-policy: 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.
put-operator-policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the put-operator-policy 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 put-operator-policy. 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.
put-operator-policy 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 →