getAffiliateUserList
Query the list of all direct client users under the current affiliate account.\nSupports cursor-based pagination. Trading volume, deposit amount, and commission data\nfor 30-day, 365-day, and custom date ranges can be returned on demand.\n\nNotes:\n- Must use an API Key with
This record as markdown: /tools/bybit-exchange-trading-mcp/getaffiliateuserlist.md
What getAffiliateUserList does on Bybit MCP Server
AI agents call getAffiliateUserList to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getAffiliateUserList is rated Low
This tool retrieves affiliate account information and statistics through query/pagination. It has no side effects, does not modify or delete data, does not execute commands, and does not involve financial transactions (it merely reports commission data rather than moving funds). The blast radius of misuse is limited to unauthorized information disclosure about affiliate users.
From the tool's definition Tool name 'getAffiliateUserList' and description 'Query the list of all direct client users' indicates data retrieval. Returns affiliate account user information, trading volume, deposit amounts, and commission data with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs getAffiliateUserList safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getAffiliateUserList, this is the rule to start with:
getAffiliateUserList 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 Bybit MCP Server, apply this rule, and every getAffiliateUserList call is checked against it from then on.
Questions about getAffiliateUserList
Query the list of all direct client users under the current affiliate account.\nSupports cursor-based pagination. Trading volume, deposit amount, and commission data\nfor 30-day, 365-day, and custom date ranges can be returned on demand.\n\nNotes:\n- Must use an API Key with. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getAffiliateUserList: 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 Bybit MCP Server. Nothing to install.
getAffiliateUserList 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 getAffiliateUserList 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 getAffiliateUserList. 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.
getAffiliateUserList is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue