getPremiumIndexPriceKline
Query historical premium index price klines, representing the basis between mark price and index price\nused in funding rate calculations for USDT and USDC perpetual contracts.\n\nUse this endpoint when you need to:\n- Analyze historical funding rate basis for perpetual contracts\n- Research the ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getpremiumindexpricekline.md
What getPremiumIndexPriceKline does on Bybit MCP Server
AI agents call getPremiumIndexPriceKline 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 getPremiumIndexPriceKline is rated Low
This tool retrieves market data (klines/candlestick data) from the Bybit exchange for analysis purposes. It has no capability to modify positions, execute trades, delete data, or move funds. The blast radius of misuse is minimal — an AI agent could only retrieve publicly available or user-owned historical pricing data, which poses low risk.
From the tool's definition Query historical premium index price klines — 'query' and 'historical' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs getPremiumIndexPriceKline 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 getPremiumIndexPriceKline, this is the rule to start with:
getPremiumIndexPriceKline 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 getPremiumIndexPriceKline call is checked against it from then on.
Questions about getPremiumIndexPriceKline
Query historical premium index price klines, representing the basis between mark price and index price\nused in funding rate calculations for USDT and USDC perpetual contracts.\n\nUse this endpoint when you need to:\n- Analyze historical funding rate basis for perpetual contracts\n- Research the relationship between mark price and index price over time\n- Build charts of the premium index (values are typically small positive or negative decimals)\n\nSupported Products: USDT perpetual, USDC perpetual\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 getPremiumIndexPriceKline: 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.
getPremiumIndexPriceKline 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 getPremiumIndexPriceKline 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 getPremiumIndexPriceKline. 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.
getPremiumIndexPriceKline 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