AI agents use create-user to create or update resources in AutoWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoWP MCP Server environment.
This tool creates a new user account, which is a reversible write operation. While it modifies the system state, user accounts can be deleted or disabled if created in error. However, the severity is high because unauthorized user creation could grant unintended access to the WordPress site, potentially compromising security if an AI agent creates privileged accounts.
From the tool's definition Tool name is 'create-user' and description states 'Create a new WordPress user account'. This creates a new user entity in the WordPress system.
Documented attack patterns abuse exactly the kind of access create-user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-user:
{
"version": "1",
"default": "deny",
"tools": {
"create-user": {
"limits": [
{
"counter": "create-user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new WordPress user account. It is categorised as a Write tool in the AutoWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoWP 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 AutoWP 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 AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.