# create_inbound

Create a new inbound on the panel. Recommend calling get_inbound on a similar existing inbound first to see the exact shape expected for settings/streamSettings/sniffing on this panel version.

Agent View of the PolicyLayer registry record for `create_inbound`. HTML page: https://policylayer.com/tools/3xui-mcp/create-inbound

## Facts

- Tool: `create_inbound`
- Server: 3xui (`3xui-mcp`) — https://policylayer.com/tools/3xui-mcp.md
- Install: `npx -y 3xui-mcp`
- Homepage: https://www.npmjs.com/package/3xui-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 9
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `port` | integer | no | Listening port |
| `enable` | boolean | no |  |
| `listen` | string | no |  |
| `remark` | string | no | Display name for the inbound |
| `protocol` | string | no | vless \| vmess \| trojan \| shadowsocks \| wireguard \| socks \| http \| dokodemo-door |
| `settings` | object | no | Protocol settings object (or JSON string), e.g. { clients: [...], decryption: "none" } |
| `sniffing` | object | no | Sniffing settings object (or JSON string), e.g. { enabled: true, destOverride: ["http","tls"] } |
| `expiryTime` | number | no |  |
| `streamSettings` | object | no | Transport settings object (or JSON string), e.g. { network: "tcp", security: "reality", ... } |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_inbound",
    "arguments": {}
  }
}
```

## Why create_inbound is rated Medium

An AI agent can call create_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.

## Use case

AI agents use create_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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 3xui:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_inbound": {
      "limits": [
        {
          "counter": "create_inbound_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 3xui (11)

- `delete_client` — Destructive — https://policylayer.com/tools/3xui-mcp/delete-client.md
- `delete_inbound` — Destructive — https://policylayer.com/tools/3xui-mcp/delete-inbound.md
- `get_client` — Read — https://policylayer.com/tools/3xui-mcp/get-client.md
- `get_client_traffic` — Read — https://policylayer.com/tools/3xui-mcp/get-client-traffic.md
- `get_inbound` — Read — https://policylayer.com/tools/3xui-mcp/get-inbound.md
- `list_clients` — Read — https://policylayer.com/tools/3xui-mcp/list-clients.md
- `list_inbounds` — Read — https://policylayer.com/tools/3xui-mcp/list-inbounds.md
- `list_online_clients` — Read — https://policylayer.com/tools/3xui-mcp/list-online-clients.md
- `create_client` — Write — https://policylayer.com/tools/3xui-mcp/create-client.md
- `update_client` — Write — https://policylayer.com/tools/3xui-mcp/update-client.md
- `update_inbound` — Write — https://policylayer.com/tools/3xui-mcp/update-inbound.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=3xui-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/3xui-mcp