get_deposit_records

What get_deposit_records does on Bybit

AI agents call get_deposit_records to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_deposit_records is rated Low

This tool queries existing financial transaction history. Reading deposit records is a read-only operation that does not move money, execute trades, or modify account state. While the data retrieved may be financially sensitive, the tool itself performs no irreversible action and has minimal blast radius if misused by an agent—it can only expose historical information already in the account.

From the tool's definition Tool name 'get_deposit_records' retrieves historical deposit records without modification. Description states 'Get deposit records' - a query operation with no side effects.

The rule that runs get_deposit_records safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_deposit_records, this is the rule to start with:

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

Questions about get_deposit_records