chart_set_visible_range
Zoom the chart to a specific date range (unix timestamps)
This record as markdown: /tools/debarpan2000-tradingview-mcp/chart-set-visible-range.md
What chart_set_visible_range does on TradingView MCP Server
AI agents invoke chart_set_visible_range to trigger actions in TradingView MCP Server. 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.
Why chart_set_visible_range is rated High
This tool performs a browser/UI action on TradingView Desktop via CDP, adjusting the visible range of a chart. It doesn't read data passively, nor does it write persistent data or delete anything. It executes an external operation (UI manipulation) whose effect is changing the chart view. The blast radius is low since it only affects the chart display state and is easily reversible by scrolling or zooming manually.
From the tool's definition 'Zoom the chart to a specific date range' — triggers an external operation (UI interaction via Chrome DevTools Protocol) that changes the chart's viewport state
Attacks that exploit this kind of access
The rule that runs chart_set_visible_range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chart_set_visible_range, this is the rule to start with:
chart_set_visible_range stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every chart_set_visible_range call is checked against it from then on.
Questions about chart_set_visible_range
Zoom the chart to a specific date range (unix timestamps). It is categorised as a Execute tool in the TradingView MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Server 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 Server. 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 Server MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TradingView MCP Server, and thousands of servers like it.
Across the catalogue