update_inbound
Update an existing inbound by ID. This replaces the inbound configuration, so fetch it with get_inbound first and merge your changes into the full object rather than sending a partial one.
This record as markdown: /tools/3xui-mcp/update-inbound.md
What update_inbound does on 3xui
AI agents use update_inbound 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 |
|---|---|---|---|
id | integer | Yes | Numeric inbound ID to update |
port | integer | — | Listening port |
enable | boolean | — | |
listen | string | — | |
remark | string | — | Display name for the inbound |
protocol | string | — | vless | vmess | trojan | shadowsocks | wireguard | socks | http | dokodemo-door |
settings | object | — | Protocol settings object (or JSON string), e.g. { clients: [...], decryption: "none" } |
sniffing | object | — | Sniffing settings object (or JSON string), e.g. { enabled: true, destOverride: ["http","tls"] } |
expiryTime | number | — | |
streamSettings | object | — | Transport settings object (or JSON string), e.g. { network: "tcp", security: "reality", ... } |
Parameters from the server's own tool schema.
Why update_inbound is rated Medium
An AI agent can call update_inbound 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 signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_inbound 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_inbound, this is the rule to start with:
update_inbound 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_inbound call is checked against it from then on.
Questions about update_inbound
Update an existing inbound by ID. This replaces the inbound configuration, so fetch it with get_inbound first and merge your changes into the full object rather than sending a partial one. 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_inbound accepts 10 parameters: id, port, enable, listen, remark, protocol, settings, sniffing, expiryTime, streamSettings. Required: id. 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_inbound: 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_inbound 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_inbound 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_inbound. 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_inbound 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