Query detailed information and status of a specified trade.\n\nQuery Options:\n- tradeNo: System-generated trade number\n- merchantRequestId: Custom merchant request ID\n\nAt least one of the above parameters must be provided.\n\nReturned Information:\n- Trade status (processing/success/failed)\n...
AI agents call queryTrade 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.
queryTrade retrieves trade information without modifying, deleting, or executing any financial transactions. It returns static trade details (status, exchange rate, timestamps) that already exist on the Bybit system. While Bybit is a financial exchange, this particular tool only reads historical trade data rather than moving money or creating new obligations.
From the tool's definition Tool description explicitly states it 'Query[s] detailed information and status of a specified trade' and lists use cases including 'Poll for trade status' and 'Display trade details to users'.
Documented attack patterns abuse exactly the kind of access queryTrade 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 queryTrade:
{
"version": "1",
"default": "deny",
"tools": {
"queryTrade": {}
}
}queryTrade 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 detailed information and status of a specified trade.\n\nQuery Options:\n- tradeNo: System-generated trade number\n- merchantRequestId: Custom merchant request ID\n\nAt least one of the above parameters must be provided.\n\nReturned Information:\n- Trade status (processing/success/failed)\n- Exchange rate information\n- Conversion amounts\n- Creation timestamp\n- User ID\n\nUse Cases:\n- Poll for trade status after submission\n- Reconcile trades using merchantRequestId\n- Display trade details to users. 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 queryTrade: 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.
queryTrade 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 queryTrade 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 queryTrade. 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.
queryTrade 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.