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 ...
AI agents call getSpreadInstrumentsInfo 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 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.
Documented attack patterns abuse exactly the kind of access getSpreadInstrumentsInfo 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 getSpreadInstrumentsInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getSpreadInstrumentsInfo": {}
}
}getSpreadInstrumentsInfo 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 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.
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.