Get OHLCV bar data from the chart. Use summary=true for compact stats instead of all bars (saves context).
AI agents call data_get_ohlcv to retrieve information from TradingView MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical price data (Open, High, Low, Close, Volume) from TradingView charts. It performs no side effects—no data is created, modified, deleted, or financial transactions initiated. It is purely informational. Even though it accesses market data used for trading decisions, the tool itself only reads and does not execute trades or commit financial obligations.
From the tool's definition Tool name 'data_get_ohlcv' and description 'Get OHLCV bar data from the chart' explicitly indicate data retrieval with no modification.
Attacks that exploit this kind of access
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 (thinhbv/tradingview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →