getAffiliateUserInfo
Query detailed information for a specified direct client user under the affiliate account,\nincluding VIP level, KYC level, wallet balance range, 30-day / 365-day trading volume,\ndeposit amount, and commission data.\n\nNotes:\n- Must use an API Key with
This record as markdown: /tools/bybit-exchange-trading-mcp/getaffiliateuserinfo.md
What getAffiliateUserInfo does on Bybit MCP Server
AI agents call getAffiliateUserInfo 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 getAffiliateUserInfo is rated Low
This tool retrieves affiliate user information without modifying any data. It is fundamentally a read operation querying account and commission details. However, severity is elevated to 'medium' rather than 'low' because the information exposed (wallet balance ranges, KYC levels, trading volumes, and commission data) is sensitive personal and financial data that could enable social engineering, fraud, or competitive…
From the tool's definition Query detailed information for a specified direct client user under the affiliate account, including VIP level, KYC level, wallet balance range, 30-day / 365-day trading volume, deposit amount, and commission data.
Attacks that exploit this kind of access
The rule that runs getAffiliateUserInfo 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 getAffiliateUserInfo, this is the rule to start with:
getAffiliateUserInfo 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 getAffiliateUserInfo call is checked against it from then on.
Questions about getAffiliateUserInfo
Query detailed information for a specified direct client user under the affiliate account,\nincluding VIP level, KYC level, wallet balance range, 30-day / 365-day trading volume,\ndeposit amount, and commission data.\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 getAffiliateUserInfo: 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.
getAffiliateUserInfo 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 getAffiliateUserInfo 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 getAffiliateUserInfo. 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.
getAffiliateUserInfo 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