chart_scroll_to_date · TradingView MCP Bridge MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why chart_scroll_to_date needs a policy

This tool executes a browser/application action (scrolling/navigating the chart view to a specific date) via CDP. It doesn't read data, write data, or delete anything — it triggers an external UI operation. Severity is low since it only affects the chart viewport position with no data modification or destructive consequences.

From the tool's definition 'Jump the chart view to center on a specific date' — triggers a UI navigation action in TradingView Desktop via Chrome DevTools Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chart_scroll_to_date Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TradingView MCP Bridge, so you can run agents against it safely.

FAQ

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

// THE FULL RECORD

chart_scroll_to_date is one line of TradingView MCP Bridge's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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