Query cryptocurrency exchange results using a quote transaction ID.\n- OpenAPI interface, requires API Key authentication\n- ACL permission: RESOURCE_GROUP_EXCHANGE_HISTORY + PERMISSION_READ\n- Rate limit: 50/path/s globally
AI agents call QueryResult 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 retrieves or queries existing exchange results/history data without modifying, executing code, deleting data, or moving funds. The explicit READ permission in the ACL and the lack of any side-effect language (create, update, delete, execute) classify this as a Read operation with low severity. The read-only nature and rate limiting (50/path/s) further support the low-risk classification.
From the tool's definition Tool name 'QueryResult' and description 'Query cryptocurrency exchange results' indicates data retrieval. The ACL permission explicitly states 'PERMISSION_READ' and the required permission is 'RESOURCE_GROUP_EXCHANGE_HISTORY', confirming read-only access to…
Documented attack patterns abuse exactly the kind of access QueryResult 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 QueryResult:
{
"version": "1",
"default": "deny",
"tools": {
"QueryResult": {}
}
}QueryResult 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 cryptocurrency exchange results using a quote transaction ID.\n- OpenAPI interface, requires API Key authentication\n- ACL permission: RESOURCE_GROUP_EXCHANGE_HISTORY + PERMISSION_READ\n- Rate limit: 50/path/s globally. 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 QueryResult: 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.
QueryResult 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 QueryResult 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 QueryResult. 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.
QueryResult 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.