Query the list of supported fiat currencies and cryptocurrencies.\n\nReturns:\n- Available fiat currencies with limits\n- Supported cryptocurrencies with limits\n- Currency status (enabled/disabled)\n- Precision information for transactions\n\nUse Cases:\n- Display available currencies to users b...
AI agents call queryCoinList 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 and lists static configuration data about supported currencies and their properties. It has no side effects—it neither modifies data, executes code, deletes anything, nor moves funds. The use cases (display, validate, show) confirm it is purely informational. This is a classic Read operation with minimal security risk if misused by an AI agent.
From the tool's definition Tool name is 'queryCoinList' and description explicitly states it 'Query[s] the list' and 'Returns: Available fiat currencies...Supported cryptocurrencies...Currency status...Precision information'.
Documented attack patterns abuse exactly the kind of access queryCoinList 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 queryCoinList:
{
"version": "1",
"default": "deny",
"tools": {
"queryCoinList": {}
}
}queryCoinList 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 list of supported fiat currencies and cryptocurrencies.\n\nReturns:\n- Available fiat currencies with limits\n- Supported cryptocurrencies with limits\n- Currency status (enabled/disabled)\n- Precision information for transactions\n\nUse Cases:\n- Display available currencies to users before trading\n- Validate currency codes before submitting quotes\n- Show transaction limits for each currency pair. 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 queryCoinList: 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.
queryCoinList 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 queryCoinList 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 queryCoinList. 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.
queryCoinList 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.