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.

SERVER3xui SOURCE3xui-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3xui-mcp/get-inbound.md

WHAT IT DOES

What get_inbound does on 3xui

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.

Parameter	Type	Required	Description
`id`	integer	Yes	Numeric inbound ID

Parameters from the server's own tool schema.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_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 get_inbound, this is the rule to start with:

get_inbound Allowed

get_inbound is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 3xui, apply this rule, and every get_inbound call is checked against it from then on.

FAQ

Questions about get_inbound

What does the get_inbound tool do? +

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. It is categorised as a Read tool in the 3xui MCP Server, which means it retrieves data without modifying state.

What parameters does get_inbound accept? +

get_inbound accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_inbound? +

Register the 3xui MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_inbound? +

get_inbound is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_inbound? +

Yes. Add a rate_limit block to the get_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.

How do I block get_inbound completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_inbound? +

get_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.

KEEP EXPLORING

More on 3xui, and thousands of servers like it.

This server

All 12 3xui tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →