queryWithdrawRecords
Query withdrawal records.\n- Master UID API key only.\n- Max 30-day range per query. If
This record as markdown: /tools/bybit-exchange-trading-mcp/querywithdrawrecords.md
What queryWithdrawRecords does on Bybit MCP Server
AI agents call queryWithdrawRecords 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 queryWithdrawRecords is rated Low
This tool retrieves historical withdrawal records from the Bybit exchange. It performs a read-only query operation—no data is created, modified, deleted, or financial transactions are executed. While it accesses sensitive account history, the read-only nature and audit trail context place it in the Read category with low severity.
From the tool's definition Tool name 'queryWithdrawRecords' and description 'Query withdrawal records' indicate data retrieval with no modification or side effects. The mention of API key restrictions and query range limits are security controls, not capability indicators.
Attacks that exploit this kind of access
The rule that runs queryWithdrawRecords 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 queryWithdrawRecords, this is the rule to start with:
queryWithdrawRecords 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 queryWithdrawRecords call is checked against it from then on.
Questions about queryWithdrawRecords
Query withdrawal records.\n- Master UID API key only.\n- Max 30-day range per query. If. 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 queryWithdrawRecords: 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.
queryWithdrawRecords 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 queryWithdrawRecords 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 queryWithdrawRecords. 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.
queryWithdrawRecords 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