# get_inbound

Get full details of a single inbound (protocol settings, stream settings, clients, traffic) by its numeric ID. Use list_inbounds first to find the ID.

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

## Facts

- Tool: `get_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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | integer | yes | Numeric inbound ID |

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": "get_inbound",
    "arguments": {
      "id": 0
    }
  }
}
```

## Why get_inbound is rated Low

Even though get_inbound only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_inbound to retrieve information from 3xui without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_inbound": {}
  }
}
```

## 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
- `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
- `create_inbound` — Write — https://policylayer.com/tools/3xui-mcp/create-inbound.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