subMemberListQuery
Query sub UIDs under the current master UID.\nReturns both all sub UIDs and the sub UIDs that have universal transfer permission.\nMaster UID API key only.
This record as markdown: /tools/bybit-exchange-trading-mcp/submemberlistquery.md
What subMemberListQuery does on Bybit MCP Server
AI agents call subMemberListQuery 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 subMemberListQuery is rated Low
This is a Read operation as it retrieves account structure and permission metadata without creating, modifying, or deleting data. Severity is elevated to medium rather than low because the information returned (sub-account UIDs and universal transfer permissions) could facilitate unauthorized transfers or account takeover if exposed to an attacker, though the tool itself performs no destructive action.
From the tool's definition Tool performs a query operation ('subMemberListQuery') that retrieves sub UIDs and transfer permissions. The description explicitly states 'Query' and 'Returns,' indicating data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs subMemberListQuery 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 subMemberListQuery, this is the rule to start with:
subMemberListQuery 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 subMemberListQuery call is checked against it from then on.
Questions about subMemberListQuery
Query sub UIDs under the current master UID.\nReturns both all sub UIDs and the sub UIDs that have universal transfer permission.\nMaster UID API key only. 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 subMemberListQuery: 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.
subMemberListQuery 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 subMemberListQuery 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 subMemberListQuery. 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.
subMemberListQuery 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