Zoom the chart to a specific date range (unix timestamps)
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.
This tool manipulates the TradingView Desktop UI by setting the visible date range on a chart. It executes a browser/application action via CDP rather than simply reading data or writing persistent data. The blast radius is low since it only affects the chart view state and is easily reversible.
From the tool's definition 'Zoom the chart to a specific date range' — triggers an external operation (UI manipulation via Chrome DevTools Protocol) on the locally running TradingView Desktop application
Documented attack patterns abuse exactly the kind of access chart_set_visible_range 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_set_visible_range:
{
"version": "1",
"default": "deny",
"tools": {
"chart_set_visible_range": {
"limits": [
{
"counter": "chart_set_visible_range_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
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.
chart_set_visible_range 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_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.
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.
chart_set_visible_range 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.
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.