getInstrumentsInfo
Query instrument specifications for active trading pairs across spot, USDT contracts,\nUSDC contracts, inverse contracts, and options markets, including price precision,\nquantity limits, leverage ranges, and contract details.\n\nUse this endpoint when you need to:\n- Discover available trading p...
This record as markdown: /tools/bybit-exchange-trading-mcp/getinstrumentsinfo.md
What getInstrumentsInfo does on Bybit MCP Server
AI agents call getInstrumentsInfo 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 getInstrumentsInfo is rated Low
This tool retrieves static or semi-static trading pair metadata (price precision, quantity limits, leverage ranges, contract details) from the Bybit exchange. It performs a query operation with no side effects, data modification, or financial impact. Misuse by an AI agent would be limited to information gathering and cannot directly cause financial loss or irreversible changes. Classified as Read with low severity.
From the tool's definition Tool description states 'Query instrument specifications' and 'Discover available trading pairs' — core read operations that retrieve market data without modification. No mutation, execution, or financial transaction occurs.
Attacks that exploit this kind of access
The rule that runs getInstrumentsInfo 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 getInstrumentsInfo, this is the rule to start with:
getInstrumentsInfo 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 getInstrumentsInfo call is checked against it from then on.
Questions about getInstrumentsInfo
Query instrument specifications for active trading pairs across spot, USDT contracts,\nUSDC contracts, inverse contracts, and options markets, including price precision,\nquantity limits, leverage ranges, and contract details.\n\nUse this endpoint when you need to:\n- Discover available trading pairs and their current trading. 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 getInstrumentsInfo: 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.
getInstrumentsInfo 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 getInstrumentsInfo 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 getInstrumentsInfo. 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.
getInstrumentsInfo 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