New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

queryInternalDepositRecords

Query deposit records occurring within the Bybit platform (not on blockchain).\n- Accessible via Master or Sub Member API Key\n- Max 30-day window between start/end times; defaults to last 30 days\n-

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/queryinternaldepositrecords.md

What queryInternalDepositRecords does on Bybit MCP Server

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

This tool retrieves deposit transaction history from the Bybit platform without modifying, deleting, or executing any operations. While the data retrieved is financially sensitive (deposit records), the tool itself only performs queries and cannot move funds, execute trades, or trigger financial transactions.

From the tool's definition Tool name 'queryInternalDepositRecords' and description 'Query deposit records occurring within the Bybit platform' indicate retrieval of historical deposit data with no modification capability.

Questions about queryInternalDepositRecords

What does the queryInternalDepositRecords tool do? +

Query deposit records occurring within the Bybit platform (not on blockchain).\n- Accessible via Master or Sub Member API Key\n- Max 30-day window between start/end times; defaults to last 30 days\n-. 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 queryInternalDepositRecords? +

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

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

Can I rate-limit queryInternalDepositRecords? +

Yes. Add a rate_limit block to the queryInternalDepositRecords 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 queryInternalDepositRecords completely? +

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bybit MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.