universalTransferListQuery
Query universal transfer records. Supports both master and sub account API keys.\n- Master API key: can query sub-sub, parent-sub, and sub-parent records where master is the operator\n- Sub account API key: can only query records where the sub account is a sender or receiver\nTime range rules:\n-...
This record as markdown: /tools/bybit-exchange-trading-mcp/universaltransferlistquery.md
What universalTransferListQuery does on Bybit MCP Server
AI agents call universalTransferListQuery 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 universalTransferListQuery is rated Low
This tool performs read-only operations on transfer history records. It retrieves and queries existing data without creating, modifying, deleting, or executing any operations. The capability to filter by account type and time range does not change its fundamental read-only nature.
From the tool's definition Tool name contains 'Query' and description states 'Query universal transfer records' with no mention of modifications, deletions, or execution. The tool retrieves historical transfer data with filtering capabilities.
Attacks that exploit this kind of access
The rule that runs universalTransferListQuery 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 universalTransferListQuery, this is the rule to start with:
universalTransferListQuery 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 universalTransferListQuery call is checked against it from then on.
Questions about universalTransferListQuery
Query universal transfer records. Supports both master and sub account API keys.\n- Master API key: can query sub-sub, parent-sub, and sub-parent records where master is the operator\n- Sub account API key: can only query records where the sub account is a sender or receiver\nTime range rules:\n- No time params: last 30 days. 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 universalTransferListQuery: 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.
universalTransferListQuery 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 universalTransferListQuery 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 universalTransferListQuery. 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.
universalTransferListQuery 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