chart_scroll_to_date

Jump the chart view to center on a specific date

SERVERTradingView MCP Bridge SOURCEbyeung888/tradingview-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about chart_scroll_to_date

What does the chart_scroll_to_date tool do? +

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.

How do I enforce a policy on chart_scroll_to_date? +

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.

What risk level is chart_scroll_to_date? +

chart_scroll_to_date is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit chart_scroll_to_date? +

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.

How do I block chart_scroll_to_date completely? +

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.

What MCP server provides chart_scroll_to_date? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TradingView MCP Bridge's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.