Create a new user
AI agents use create_user to create or update resources in FastAPI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FastAPI MCP Server environment.
Creating a user is a reversible write operation that modifies system state by adding a new entity. It is not destructive (data can be deleted), not financial, and not execution of arbitrary code. The severity is medium because user creation could enable unauthorized account proliferation or privilege escalation if misused by an AI agent, but the operation itself is not catastrophic and can be undone via delete_user.
From the tool's definition Tool name 'create_user' and description 'Create a new user' indicate this tool creates and persists a new user record in the system.
Attacks that exploit this kind of access
Create a new user. It is categorised as a Write tool in the FastAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FastAPI 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 FastAPI 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 FastAPI MCP Server MCP server (teeps-heisenberg/mcp-server-fast-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 →