update_client
Update an existing client's traffic limit, expiry, or enabled state. Only the fields you pass are changed; everything else on the client is preserved.
This record as markdown: /tools/3xui-mcp/update-client.md
What update_client does on 3xui
AI agents use update_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 |
|---|---|---|---|
enable | boolean | — | Enable or disable the client |
limitIp | integer | — | New max simultaneous IPs (0 = unlimited) |
totalGB | number | — | New data limit in GB (0 = unlimited) |
clientId | string | Yes | Client UUID (VLESS/VMess) or password (Trojan/Shadowsocks) — see get_client |
inboundId | integer | Yes | Numeric ID of the inbound the client belongs to |
expiryDays | integer | — | Alternative to expiryTime: set expiry to N days from now |
expiryTime | integer | — | New expiry as a Unix ms timestamp (0 = never) |
Parameters from the server's own tool schema.
Why update_client is rated Medium
An AI agent can call update_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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs update_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 update_client, this is the rule to start with:
update_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 update_client call is checked against it from then on.
Questions about update_client
Update an existing client's traffic limit, expiry, or enabled state. Only the fields you pass are changed; everything else on the client is preserved. 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.
update_client accepts 7 parameters: enable, limitIp, totalGB, clientId, inboundId, expiryDays, expiryTime. Required: clientId, 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 update_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.
update_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 update_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 update_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.
update_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