Zoom the chart to a specific date range (unix timestamps)
AI agents invoke chart_set_visible_range to trigger actions in TradingView MCP Jackson. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool controls the TradingView Desktop application by setting the visible date range on a chart. It triggers an external operation (UI manipulation via CDP) rather than simply reading data or writing persistent data. The blast radius is low since it only affects chart view state and is easily reversible by scrolling or zooming.
From the tool's definition 'Zoom the chart to a specific date range (unix timestamps)' — triggers an external UI operation on TradingView Desktop via Chrome DevTools Protocol
Attacks that exploit this kind of access
Zoom the chart to a specific date range (unix timestamps). It is categorised as a Execute tool in the TradingView MCP Jackson MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Jackson MCP server in PolicyLayer and add a rule for chart_set_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_set_visible_range is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chart_set_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_set_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_set_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 →