queryWithdrawAddresses
Retrieve withdrawal addresses from the address book.\n- API key must have withdrawal permissions.\n- Business rules (from code):\n - When addressType is 1 (internal transfer) or 2 (all), coin and chain parameters are ignored\n - Records with failed address signature verification will be filtered ...
This record as markdown: /tools/bybit-exchange-trading-mcp/querywithdrawaddresses.md
What queryWithdrawAddresses does on Bybit MCP Server
AI agents call queryWithdrawAddresses 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 queryWithdrawAddresses is rated Low
This tool retrieves data (withdrawal addresses from an address book) without creating, modifying, or deleting records. It is a Read operation. However, severity is elevated to medium rather than low because: (1) the data retrieved includes sensitive withdrawal addresses associated with the user's account, which could be valuable if an AI agent leaked or logged this information; (2) the tool requires withdrawal…
From the tool's definition Tool name "queryWithdrawAddresses" and description "Retrieve withdrawal addresses" indicates a query/retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs queryWithdrawAddresses 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 queryWithdrawAddresses, this is the rule to start with:
queryWithdrawAddresses 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 queryWithdrawAddresses call is checked against it from then on.
Questions about queryWithdrawAddresses
Retrieve withdrawal addresses from the address book.\n- API key must have withdrawal permissions.\n- Business rules (from code):\n - When addressType is 1 (internal transfer) or 2 (all), coin and chain parameters are ignored\n - Records with failed address signature verification will be filtered out\n - If user has enabled 24-hour new address no-verification security policy, new address status=1 means unavailable within 24 hours\n - Use baseCoin as coin to query universal addresses. 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 queryWithdrawAddresses: 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.
queryWithdrawAddresses 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 queryWithdrawAddresses 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 queryWithdrawAddresses. 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.
queryWithdrawAddresses 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