create_user
AI agents use create_user to create or update resources in Amazon MQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon MQ MCP Server environment.
Creating users in a message broker (AMQ) is a Write operation—it creates new data/identities that are reversible through deletion. While the description is empty (lowering confidence slightly), the tool name is unambiguous. Severity is 'high' because unauthorized user creation could grant an attacker broker access, credentials, or message queue permissions. However, it's not Destructive (reversible) or Financial.
From the tool's definition Tool named 'create_user' on an Amazon MQ server that manages AMQ brokers. The name explicitly indicates user creation, a write operation that creates new identity/access entities.
Attacks that exploit this kind of access
create_user. It is categorised as a Write tool in the Amazon MQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for create_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 Amazon MQ MCP Server. Nothing to install.
create_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 create_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 create_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.
create_user is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.