AI agents use put-user 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 | |
tags | string | — | |
password | string | — |
Parameters from the server's own tool schema.
This tool modifies user records in RabbitMQ, which is a Write-category operation. It is reversible (users can be deleted or re-updated), so it does not qualify as Destructive. The severity is medium because unauthorized user creation/modification in a message broker could enable unauthorized access or privilege escalation, but the impact is localized to identity management rather than system-wide data loss.
From the tool's definition Tool name is 'put-user' with description 'Create or update a user.' The verbs 'create or update' indicate reversible modification of user data.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
Create or update a user. 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-user accepts 3 parameters: name, tags, password. Required: name. 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-user: 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-user 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-user 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-user. 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-user 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 →