This record as markdown: /tools/aiwerk-mcp-server-ghl/users-create-user.md
What users_create_user does on Ghl
AI agents use users_create_user to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | Yes | |
type | string | Yes | |
email | string | Yes | |
phone | string | — | |
scopes | array | — | Scopes allowed for users. Only scopes that have been passed will be enabled. Note:- If passed empty all the scopes will be get disabled |
lastName | string | Yes | |
password | string | Yes | |
companyId | string | Yes | |
firstName | string | Yes | |
locationIds | array | Yes | |
permissions | object | — | |
twilioPhone | object | — | Per-location inbound Twilio number in E.164 format, keyed by location id (Call and Voicemail Inbound Number for direct Twilio, not LC Phone). Replacement semant |
Parameters from the server's own tool schema.
Why users_create_user is rated Medium
An AI agent can call users_create_user faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (password) · High parameter count (53 properties)
Attacks that exploit this kind of access
The rule that runs users_create_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users_create_user, this is the rule to start with:
users_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 Ghl, apply this rule, and every users_create_user call is checked against it from then on.
Questions about users_create_user
Create User. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
users_create_user accepts 12 parameters: role, type, email, phone, scopes, lastName, password, companyId, firstName, locationIds, permissions, twilioPhone. Required: role, type, email, lastName, password, companyId, firstName, locationIds. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for users_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 Ghl. Nothing to install.
users_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 users_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 users_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.
users_create_user is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue