create_client
Create a new client on an existing inbound with auto-generated credentials (UUID/password/keys as appropriate for the protocol). Returns the generated credentials and connection info — surface these to the user, they are not retrievable again in plaintext.
This record as markdown: /tools/3xui-mcp/create-client.md
What create_client does on 3xui
AI agents use create_client to create or update resources in 3xui, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 3xui environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Unique email/identifier for the new client |
limitIp | integer | — | Max simultaneous IPs (0 = unlimited) |
totalGB | number | — | Data limit in GB (0 = unlimited). Converted to bytes automatically. |
protocol | string | Yes | Protocol to generate credentials for |
inboundId | integer | Yes | Numeric ID of the inbound to add the client to (see list_inbounds) |
expiryTime | integer | — | Expiry as a Unix ms timestamp (0 = never) |
Parameters from the server's own tool schema.
Why create_client is rated Medium
An AI agent can call create_client faster than any human can review: one bad instruction and it creates or modifies resources in 3xui by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_client safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3xui, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_client, this is the rule to start with:
create_client 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 3xui, apply this rule, and every create_client call is checked against it from then on.
Questions about create_client
Create a new client on an existing inbound with auto-generated credentials (UUID/password/keys as appropriate for the protocol). Returns the generated credentials and connection info — surface these to the user, they are not retrievable again in plaintext. It is categorised as a Write tool in the 3xui MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_client accepts 6 parameters: email, limitIp, totalGB, protocol, inboundId, expiryTime. Required: email, protocol, inboundId. The full parameter table on this page comes from the server's own tool schema.
Register the 3xui MCP server in PolicyLayer and add a rule for create_client: 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 3xui. Nothing to install.
create_client 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_client 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_client. 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_client is provided by the 3xui MCP server (3xui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3xui, and thousands of servers like it.
This server
Across the catalogue