Get a complete list of all sub-accounts under the master account. Use master account
AI agents call querySubMembers to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about sub-accounts without creating, modifying, or deleting data, and without executing financial transactions. It is a pure read operation. Severity is medium rather than low because sub-account information could reveal account structure and holdings to an unauthorized party if credentials are compromised, presenting meaningful risk if misused by a compromised AI agent.
From the tool's definition Tool name 'querySubMembers' and description 'Get a complete list of all sub-accounts under the master account' indicate data retrieval with no modification or execution of trades/operations.
Documented attack patterns abuse exactly the kind of access querySubMembers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for querySubMembers:
{
"version": "1",
"default": "deny",
"tools": {
"querySubMembers": {}
}
}querySubMembers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a complete list of all sub-accounts under the master account. Use master account. 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 querySubMembers: 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.
querySubMembers 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 querySubMembers 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 querySubMembers. 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.
querySubMembers 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.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.