High Risk →

chart_scroll_to_date

Jump the chart view to center on a specific date

How to control chart_scroll_to_date ↓

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.

High Risk

This tool triggers an external UI operation in TradingView Desktop (scrolling/navigating the chart view), which is an action executed against a running application via Chrome DevTools Protocol. It doesn't read data, write/create data persistently, or have financial/destructive impact — it manipulates the application's viewport state, making Execute the most appropriate category.

From the tool's definition Jump the chart view to center on a specific date

Documented attack patterns abuse exactly the kind of access chart_scroll_to_date gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for chart_scroll_to_date:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "chart_scroll_to_date": {
      "limits": [
        {
          "counter": "chart_scroll_to_date_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register TradingView MCP Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

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 (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TradingView MCP Bridge tool call.

Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.