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