get_client_traffic
Get upload/download traffic totals and limits for a single client by exact email.
This record as markdown: /tools/3xui-mcp/get-client-traffic.md
What get_client_traffic does on 3xui
AI agents call get_client_traffic 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 |
|---|---|---|---|
email | string | Yes | Exact client email/identifier |
Parameters from the server's own tool schema.
Why get_client_traffic is rated Low
Even though get_client_traffic 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
The rule that runs get_client_traffic 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_client_traffic, this is the rule to start with:
get_client_traffic is read-only, so it stays allowed. 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 get_client_traffic call is checked against it from then on.
Questions about get_client_traffic
Get upload/download traffic totals and limits for a single client by exact email. It is categorised as a Read tool in the 3xui MCP Server, which means it retrieves data without modifying state.
get_client_traffic accepts 1 parameter: email. Required: email. 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 get_client_traffic: 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.
get_client_traffic is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_client_traffic 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 get_client_traffic. 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.
get_client_traffic 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