Zoom in/out by a factor. factor > 1 = zoom in (fewer bars visible), factor < 1 = zoom out (more bars). Use
AI agents invoke chart_zoom to trigger actions in TradingView MCP. 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 triggers an external operation (manipulating the TradingView Desktop chart view via Chrome DevTools Protocol) that changes the visible state of the application. It doesn't read, write persistent data, or destroy data, but it executes a UI/application action that modifies the chart viewport. Severity is medium as misuse could disrupt trading analysis sessions but has no financial or data-destruction impact.
From the tool's definition Zoom in/out by a factor. factor > 1 = zoom in (fewer bars visible), factor < 1 = zoom out (more bars)
Attacks that exploit this kind of access
Zoom in/out by a factor. factor > 1 = zoom in (fewer bars visible), factor < 1 = zoom out (more bars). Use. It is categorised as a Execute tool in the TradingView MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP server in PolicyLayer and add a rule for chart_zoom: 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. Nothing to install.
chart_zoom 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_zoom 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_zoom. 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_zoom is provided by the TradingView MCP server (ulianbass/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →