getIndexPriceKline
Query historical index price klines derived from the composite spot price across multiple exchanges.\n\nUse this endpoint when you need to:\n- Analyze historical index price movements for research or backtesting\n- Compare index price vs mark price to understand basis spread over time\n- Build ch...
This record as markdown: /tools/bybit-exchange-trading-mcp/getindexpricekline.md
What getIndexPriceKline does on Bybit MCP Server
AI agents call getIndexPriceKline 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 getIndexPriceKline is rated Low
getIndexPriceKline retrieves and queries historical market data without creating, modifying, or deleting any data. It has no capability to execute trades, modify positions, move funds, or alter any state on the exchange. The blast radius of misuse is minimal — an AI agent could only retrieve historical price information, which poses no financial or operational risk to the user's account.
From the tool's definition Tool description explicitly states 'Query historical index price klines' and use cases are limited to 'Analyze historical index price movements for research or backtesting' and 'Compare index price vs mark price' — all read-only data retrieval operations with…
Attacks that exploit this kind of access
The rule that runs getIndexPriceKline 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 getIndexPriceKline, this is the rule to start with:
getIndexPriceKline 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 getIndexPriceKline call is checked against it from then on.
Questions about getIndexPriceKline
Query historical index price klines derived from the composite spot price across multiple exchanges.\n\nUse this endpoint when you need to:\n- Analyze historical index price movements for research or backtesting\n- Compare index price vs mark price to understand basis spread over time\n- Build charts of the underlying spot market price reference used by Bybit\n\nSupported Products: USDT contract, USDC contract, Inverse contract\n\nEach kline entry is a 5-element array:. 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 getIndexPriceKline: 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.
getIndexPriceKline 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 getIndexPriceKline 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 getIndexPriceKline. 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.
getIndexPriceKline 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