Low Risk

data_get_ohlcv

Get OHLCV bar data from the chart. Use summary=true for compact stats instead of all bars (saves context).

How to control data_get_ohlcv ↓

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.

Low Risk

This tool retrieves historical price and volume data from a chart without modifying, deleting, or executing any operations. It is a pure read operation that returns financial data. While the data pertains to trading (financial markets), the tool itself does not move money, create positions, or commit financial obligations—it only retrieves information. Therefore, it is classified as Read rather than Financial.

From the tool's definition Tool description states 'Get OHLCV bar data from the chart' with options for 'compact stats instead of all bars'. The verb 'Get' and the data retrieval nature (OHLCV = Open, High, Low, Close, Volume) indicate a query operation with no side effects.

Documented attack patterns abuse exactly the kind of access data_get_ohlcv gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for data_get_ohlcv:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "data_get_ohlcv": {}
  }
}

data_get_ohlcv is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register TradingView MCP Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the data_get_ohlcv tool do? +

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.

How do I enforce a policy on data_get_ohlcv? +

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.

What risk level is data_get_ohlcv? +

data_get_ohlcv is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit data_get_ohlcv? +

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.

How do I block data_get_ohlcv completely? +

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.

What MCP server provides data_get_ohlcv? +

data_get_ohlcv is provided by the TradingView MCP Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TradingView MCP Bridge tool call.

Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.