chart_scroll_to_date
Jump the chart view to center on a specific date
This record as markdown: /tools/byeung888-tradingview-mcp/chart-scroll-to-date.md
What chart_scroll_to_date does on TradingView MCP Bridge
AI agents invoke chart_scroll_to_date to trigger actions in TradingView MCP Bridge. 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_scroll_to_date is rated High
This tool performs a UI action on a locally running application (TradingView Desktop) via CDP, which constitutes triggering an external operation. It doesn't read data, write/modify data, or delete anything — it navigates the chart view to a specific date. The blast radius is low since it only affects the chart viewport position with no financial, destructive, or persistent side effects.
From the tool's definition 'Jump the chart view to center on a specific date' — triggers an external operation (scrolling/navigating the TradingView Desktop chart UI) via Chrome DevTools Protocol
Attacks that exploit this kind of access
The rule that runs chart_scroll_to_date safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chart_scroll_to_date, this is the rule to start with:
chart_scroll_to_date 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 Bridge, apply this rule, and every chart_scroll_to_date call is checked against it from then on.
Questions about chart_scroll_to_date
Jump the chart view to center on a specific date. It is categorised as a Execute tool in the TradingView MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for chart_scroll_to_date: 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_scroll_to_date 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_scroll_to_date 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_scroll_to_date. 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_scroll_to_date is provided by the TradingView MCP Bridge MCP server (byeung888/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 Bridge, and thousands of servers like it.
Across the catalogue