stateset_create_user
Creates a new user account. Requires email, name, role, and password. Roles: admin, manager, operator, viewer.
This record as markdown: /tools/stateset-mcp-server/stateset-create-user.md
What stateset_create_user does on Stateset
AI agents use stateset_create_user to create or update resources in Stateset, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stateset environment.
Why stateset_create_user is rated Medium
This tool creates new data (user account) reversibly, fitting the Write category. Severity is high because user creation with role assignment can grant significant system access (including admin roles), and misuse could create unauthorized privileged accounts for persistence or lateral movement. However, it is not Destructive (reversible via account deletion) nor Financial.
From the tool's definition Tool description states 'Creates a new user account' with required parameters including role assignment (admin, manager, operator, viewer), which modifies system state by adding a new user with specific permissions.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs stateset_create_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_create_user, this is the rule to start with:
stateset_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_create_user call is checked against it from then on.
Questions about stateset_create_user
Creates a new user account. Requires email, name, role, and password. Roles: admin, manager, operator, viewer. It is categorised as a Write tool in the Stateset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_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 Stateset. Nothing to install.
stateset_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 stateset_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 stateset_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.
stateset_create_user is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
This server
Across the catalogue