Query historical mark price klines used for margin and liquidation calculations in derivative contracts.\n\nUse this endpoint when you need to:\n- Analyze historical mark price movements for risk management or backtesting\n- Chart mark price candles alongside trading price candles for comparison\...
AI agents call getMarkPriceKline 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 is a data retrieval tool that queries historical mark price information for analysis and charting purposes. It has no side effects, does not create, modify, or delete data, and does not execute trades or financial transactions. The tool is informational for risk management and backtesting only.
From the tool's definition Tool name and description indicate querying historical mark price data: 'Query historical mark price klines', 'Analyze historical mark price movements', 'Chart mark price candles', 'Understand liquidation risk over time'.
Documented attack patterns abuse exactly the kind of access getMarkPriceKline 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 getMarkPriceKline:
{
"version": "1",
"default": "deny",
"tools": {
"getMarkPriceKline": {}
}
}getMarkPriceKline 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 mark price klines used for margin and liquidation calculations in derivative contracts.\n\nUse this endpoint when you need to:\n- Analyze historical mark price movements for risk management or backtesting\n- Chart mark price candles alongside trading price candles for comparison\n- Understand liquidation risk over time based on mark price history\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 getMarkPriceKline: 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.
getMarkPriceKline 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 getMarkPriceKline 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 getMarkPriceKline. 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.
getMarkPriceKline 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.