clerk.create_user
Create a user in a connected Clerk application. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Cost = 10 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.create-user.md
What clerk.create_user does on Vee3
AI agents use clerk.create_user to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
password | object | — | Optional password. Omit to create a user without a password. |
last_name | object | — | Optional last name. |
first_name | object | — | Optional first name. |
email_address | string | Yes | Primary email address for the new Clerk user. |
clerk_instance_id | object | — | Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account. |
Parameters from the server's own tool schema.
Why clerk.create_user is rated Medium
Creates user accounts reversibly in Clerk, high blast radius if abused for spam or unauthorized access provisioning.
From the tool's definition Create a user in a connected Clerk application
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs clerk.create_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clerk.create_user, this is the rule to start with:
clerk.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 Vee3, apply this rule, and every clerk.create_user call is checked against it from then on.
Questions about clerk.create_user
Create a user in a connected Clerk application. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Cost = 10 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
clerk.create_user accepts 5 parameters: password, last_name, first_name, email_address, clerk_instance_id. Required: email_address. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for clerk.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 Vee3. Nothing to install.
clerk.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 clerk.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 clerk.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.
clerk.create_user is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue