chart_set_visible_range · TradingView MCP Bridge MCP

WHAT IT DOES

What chart_set_visible_range does on TradingView MCP Bridge

AI agents invoke chart_set_visible_range 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_set_visible_range needs a policy

This tool controls the visible range of a TradingView chart by interacting with an external desktop application. It does not read data, write/create data, or destroy anything — it executes an action (UI manipulation via CDP) that changes the chart view state. Misuse has minimal blast radius as it only affects the chart's zoom/view.

From the tool's definition 'Zoom the chart to a specific date range' — triggers an external operation on TradingView Desktop charts via Chrome DevTools Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chart_set_visible_range Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chart_set_visible_range": {
      "limits": [
        {
          "counter": "chart_set_visible_range_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_set_visible_range

What does the chart_set_visible_range tool do? +

Zoom the chart to a specific date range (unix timestamps). 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_set_visible_range? +

Register the TradingView MCP Bridge 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 Bridge. Nothing to install.

What risk level is chart_set_visible_range? +

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

Can I rate-limit chart_set_visible_range? +

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.

How do I block chart_set_visible_range completely? +

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.

What MCP server provides chart_set_visible_range? +

chart_set_visible_range 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_set_visible_range 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 →