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 Jackson without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns chart state information (visible date range and bar indices). It is purely observational—no data is created, modified, deleted, or executed. Classification as Read is appropriate because it retrieves metadata about the current chart view without triggering any actions or state changes.
From the tool's definition Tool description states it 'Get[s] the visible date range (unix timestamps) and bars range on the chart' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the visible date range (unix timestamps) and bars range on the chart. It is categorised as a Read tool in the TradingView MCP Jackson MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Jackson 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 Jackson. 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 Jackson MCP server (nimit791/tradingview-mcp-jackson). 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 →