getSpreadInstrumentsInfo
Query instrument specifications for spread combination trading pairs, including\ncontract type, trading status, price tick size, order quantity limits, and component\nleg instrument details.\n\nUse this endpoint when you need to:\n- Discover available spread symbols and their trading constraints ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getspreadinstrumentsinfo.md
What getSpreadInstrumentsInfo does on Bybit MCP Server
AI agents call getSpreadInstrumentsInfo 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 getSpreadInstrumentsInfo is rated Low
This tool retrieves and queries financial instrument metadata from the Bybit exchange. It has no capability to modify positions, execute trades, transfer funds, or perform destructive operations. It is purely informational, helping users understand trading constraints before placing orders.
From the tool's definition Tool name 'getSpreadInstrumentsInfo' and description 'Query instrument specifications' — queries data about spread trading pairs, contract types, trading status, price tick size, order quantity limits, and component leg details.
Attacks that exploit this kind of access
The rule that runs getSpreadInstrumentsInfo 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 getSpreadInstrumentsInfo, this is the rule to start with:
getSpreadInstrumentsInfo 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 getSpreadInstrumentsInfo call is checked against it from then on.
Questions about getSpreadInstrumentsInfo
Query instrument specifications for spread combination trading pairs, including\ncontract type, trading status, price tick size, order quantity limits, and component\nleg instrument details.\n\nUse this endpoint when you need to:\n- Discover available spread symbols and their trading constraints before placing orders\n- Validate price precision (. 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 getSpreadInstrumentsInfo: 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.
getSpreadInstrumentsInfo 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 getSpreadInstrumentsInfo 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 getSpreadInstrumentsInfo. 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.
getSpreadInstrumentsInfo 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