list_inbounds

List every inbound configured on the 3x-ui panel, including their clients, protocol, port, and traffic stats.

SERVER3xui SOURCE3xui-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3xui-mcp/list-inbounds.md

WHAT IT DOES

What list_inbounds does on 3xui

AI agents call list_inbounds 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.

RISK

Why list_inbounds is rated Low

Even though list_inbounds 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_inbounds Allowed

list_inbounds 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": {
    "list_inbounds": {}
  }
}

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 list_inbounds call is checked against it from then on.

FAQ

Questions about list_inbounds

What does the list_inbounds tool do? +

List every inbound configured on the 3x-ui panel, including their clients, protocol, port, and traffic stats. It is categorised as a Read tool in the 3xui MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_inbounds? +

Register the 3xui MCP server in PolicyLayer and add a rule for list_inbounds: 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 list_inbounds? +

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

Can I rate-limit list_inbounds? +

Yes. Add a rate_limit block to the list_inbounds 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 list_inbounds completely? +

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

list_inbounds 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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