data_get_ohlcv
Get OHLCV bar data from the chart. Use summary=true for compact stats instead of all bars (saves context).
This record as markdown: /tools/byeung888-tradingview-mcp/data-get-ohlcv.md
What data_get_ohlcv does on TradingView MCP Bridge
AI agents call data_get_ohlcv to retrieve information from TradingView MCP Bridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why data_get_ohlcv is rated Low
This tool retrieves historical OHLCV (Open, High, Low, Close, Volume) data from charts without any side effects. It performs read-only queries of existing market data. No data is created, modified, deleted, or used to trigger external transactions. The severity is low as misuse would only affect information access, not data integrity or financial operations.
From the tool's definition Tool name 'data_get_ohlcv' and description 'Get OHLCV bar data from the chart' indicates data retrieval with no modification. The mention of 'summary=true for compact stats' confirms it is a query operation with optional output formatting.
Attacks that exploit this kind of access
The rule that runs data_get_ohlcv safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_get_ohlcv, this is the rule to start with:
data_get_ohlcv 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 TradingView MCP Bridge, apply this rule, and every data_get_ohlcv call is checked against it from then on.
Questions about data_get_ohlcv
Get OHLCV bar data from the chart. Use summary=true for compact stats instead of all bars (saves context). It is categorised as a Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for data_get_ohlcv: 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 TradingView MCP Bridge. Nothing to install.
data_get_ohlcv 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 data_get_ohlcv 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 data_get_ohlcv. 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.
data_get_ohlcv is provided by the TradingView MCP Bridge MCP server (byeung888/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TradingView MCP Bridge, and thousands of servers like it.
This server
Across the catalogue