querySubMemberDepositRecords

What querySubMemberDepositRecords does on Bybit MCP Server

AI agents call querySubMemberDepositRecords 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 querySubMemberDepositRecords is rated Low

This tool retrieves deposit records for a sub-account, which is a read-only operation with no side effects. However, the sensitivity is elevated to medium severity because: (1) it accesses financial transaction history that could reveal account activity, holdings, and user patterns; (2) it operates on a sub-account via main UID credentials, indicating privileged access; (3) misuse by an AI agent could leak sensitive…

From the tool's definition Tool name 'querySubMemberDepositRecords' and description 'Query on-chain deposit records' indicate data retrieval. The phrase 'Query' and 'deposit records' confirm a read operation that retrieves historical transaction data without modification.

The rule that runs querySubMemberDepositRecords 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 querySubMemberDepositRecords, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "querySubMemberDepositRecords": {}
  }
}

Questions about querySubMemberDepositRecords