Get the visible date range (unix timestamps) and bars range on the chart
AI agents call chart_get_visible_range 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 is a passive data retrieval operation that returns information about the current state of a chart (visible date ranges and bars). It has no side effects, does not modify data, and does not trigger external operations. It is clearly a Read operation, which carries minimal security risk unless the returned data itself were sensitive, which timestamp and bar range information is not in a trading context.
From the tool's definition The tool retrieves 'the visible date range (unix timestamps) and bars range on the chart' — it queries current chart state without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access chart_get_visible_range 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 chart_get_visible_range:
{
"version": "1",
"default": "deny",
"tools": {
"chart_get_visible_range": {}
}
}chart_get_visible_range 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.
Get the visible date range (unix timestamps) and bars range on the chart. 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 chart_get_visible_range: 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.
chart_get_visible_range 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 chart_get_visible_range 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 chart_get_visible_range. 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.
chart_get_visible_range 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.
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.