get_kline
Get historical candlestick/OHLC data for technical analysis. Returns open, high, low, close prices and volume data. If no time range specified, returns recent data ending at current time.
This record as markdown: /tools/bcusack-bybit-py-mcp/get-kline.md
What get_kline does on Bybit MCP Server
AI agents call get_kline 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 get_kline is rated Low
This tool only queries and returns historical market data (OHLC candlestick information). It performs no write operations, executes no code, deletes nothing, and moves no money. Even in a financial trading context, reading market data poses minimal risk as it cannot directly cause financial harm or unintended trades. The blast radius of misuse is limited to potential information leakage or API rate limiting.
From the tool's definition Tool is described as 'Get historical candlestick/OHLC data' which retrieves price data without side effects. The term 'Get' and the purpose for 'technical analysis' indicate pure data retrieval with no modifications to account state, positions, or balances.
Attacks that exploit this kind of access
The rule that runs get_kline 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 get_kline, this is the rule to start with:
get_kline 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 get_kline call is checked against it from then on.
Questions about get_kline
Get historical candlestick/OHLC data for technical analysis. Returns open, high, low, close prices and volume data. If no time range specified, returns recent data ending at current time. 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 get_kline: 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.
get_kline 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 get_kline 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 get_kline. 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.
get_kline is provided by the Bybit MCP Server MCP server (bcusack/bybit-py-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