querySubMemberDepositAddress
Query deposit address for a sub-account. Requires master UID API key only.\n- Custodial sub-account addresses are unavailable\n- Validates parent-child relationship between master and sub accounts\n- Sub-accounts bound to Copper custody are not allowed\n- UAE coin restrictions apply
This record as markdown: /tools/bybit-exchange-trading-mcp/querysubmemberdepositaddress.md
What querySubMemberDepositAddress does on Bybit MCP Server
AI agents call querySubMemberDepositAddress 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 querySubMemberDepositAddress is rated Low
This tool retrieves deposit address information for cryptocurrency sub-accounts. It performs no write operations, executes no external code, deletes nothing, and moves no funds. While it requires master UID API key and involves a cryptocurrency exchange, the operation itself is a straightforward data retrieval with read-only side effects (validation checks).
From the tool's definition Tool name includes 'query' and description states it 'Query deposit address for a sub-account' — purely retrieves account address information with no modifications or irreversible actions.
Attacks that exploit this kind of access
The rule that runs querySubMemberDepositAddress 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 querySubMemberDepositAddress, this is the rule to start with:
querySubMemberDepositAddress 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 querySubMemberDepositAddress call is checked against it from then on.
Questions about querySubMemberDepositAddress
Query deposit address for a sub-account. Requires master UID API key only.\n- Custodial sub-account addresses are unavailable\n- Validates parent-child relationship between master and sub accounts\n- Sub-accounts bound to Copper custody are not allowed\n- UAE coin restrictions apply. 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 querySubMemberDepositAddress: 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.
querySubMemberDepositAddress 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 querySubMemberDepositAddress 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 querySubMemberDepositAddress. 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.
querySubMemberDepositAddress 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