queryDepositRecords

Query on-chain deposit records\n- Supports both main and sub UID API keys\n- Time range (

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/querydepositrecords.md

WHAT IT DOES

What queryDepositRecords does on Bybit MCP Server

AI agents call queryDepositRecords 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.

RISK

Why queryDepositRecords is rated Low

This tool queries historical deposit records, which is a pure data retrieval operation with no side effects. It does not create, modify, or delete data, nor does it execute trades or move funds. While it provides financial information (deposit history), it does not move money or commit financial obligations itself—it only reads existing transaction records.

From the tool's definition Tool name 'queryDepositRecords' and description 'Query on-chain deposit records' indicate a read-only retrieval operation with no data modification, deletion, or financial transaction execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

queryDepositRecords Allowed

queryDepositRecords is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every queryDepositRecords call is checked against it from then on.

FAQ

Questions about queryDepositRecords

What does the queryDepositRecords tool do? +

Query on-chain deposit records\n- Supports both main and sub UID API keys\n- Time range (. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on queryDepositRecords? +

Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for queryDepositRecords: 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.

What risk level is queryDepositRecords? +

queryDepositRecords is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit queryDepositRecords? +

Yes. Add a rate_limit block to the queryDepositRecords 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.

How do I block queryDepositRecords completely? +

Set action: deny in the PolicyLayer policy for queryDepositRecords. 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.

What MCP server provides queryDepositRecords? +

queryDepositRecords 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.

KEEP EXPLORING

More on Bybit MCP Server, and thousands of servers like it.

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →