Query the internal transfer records between different account types under the same UID.\nTime range rules:\n- No time params: last 30 days (default)
AI agents call interTransferListQuery to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and retrieves existing internal transfer records between account types. It has no side effects, does not modify data, execute commands, or affect financial transactions. The time range rules indicate it simply filters historical data. This is a straightforward read operation with minimal risk.
From the tool's definition Tool name contains 'Query' and description states it 'Query the internal transfer records' — retrieves historical transfer data with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access interTransferListQuery gives an agent:
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 interTransferListQuery:
{
"version": "1",
"default": "deny",
"tools": {
"interTransferListQuery": {}
}
}interTransferListQuery is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query the internal transfer records between different account types under the same UID.\nTime range rules:\n- No time params: last 30 days (default). 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 interTransferListQuery: 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.
interTransferListQuery 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 interTransferListQuery 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 interTransferListQuery. 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.
interTransferListQuery 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.
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.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.