queryWithdrawRecords

THE RISK

Low Risk

Why queryWithdrawRecords needs a policy

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.

Documented attack patterns abuse exactly the kind of access queryWithdrawRecords gives an agent:

POLICY

How to control queryWithdrawRecords

PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for queryWithdrawRecords:

policy.json

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

queryWithdrawRecords is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Bybit MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bybit MCP Server tools

Financial removeLiquidity Withdraw funds from a Liquidity Mining pool position.\n\n- Financial confirmQuote Confirm the quote and execute the conversion trade.\n\nImportant:\n- Must confirm within t Financial executePurchase Place a buy order to purchase on-chain tokens with payment tokens.\nReturns an Financial executeQuote Execute (accept) a quote to initiate the multi-leg trade.\nThis endpoint is asynchronous - Financial executeRedeem Place a sell order to redeem on-chain tokens for payment tokens.\nReturns an Financial quickRepayment Execute quick repayment for specified coin Financial accountBorrow Manual borrow for Unified account.\n\nRules:\n- Borrowing via OpenAPI endpoint supports va Financial accountRepay Manually repay the liabilities of Unified account.\n\nRules:\n- If neither

All 326 Bybit MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about queryWithdrawRecords

What does the queryWithdrawRecords tool do? +

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.

How do I enforce a policy on queryWithdrawRecords? +

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.

What risk level is queryWithdrawRecords? +

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

Can I rate-limit queryWithdrawRecords? +

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.

How do I block queryWithdrawRecords completely? +

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.

What MCP server provides queryWithdrawRecords? +

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.

Enforce policy on every Bybit MCP Server tool call.

Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →