Switch to a saved chart layout by name or ID
AI agents invoke layout_switch to trigger actions in TradingView MCP Jackson. 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 performs an action in an external application (TradingView Desktop) by switching the active layout. It is not a simple read, nor does it create/modify data reversibly in a database sense — it triggers a UI-level operation via Chrome DevTools Protocol. Misuse could disrupt a trader's active workspace or cause unintended chart views during live trading sessions, warranting medium severity.
From the tool's definition Switch to a saved chart layout by name or ID — triggers an external operation in TradingView Desktop via CDP, changing the active UI state
Attacks that exploit this kind of access
Switch to a saved chart layout by name or ID. It is categorised as a Execute tool in the TradingView MCP Jackson MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Jackson MCP server in PolicyLayer and add a rule for layout_switch: 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 Jackson. Nothing to install.
layout_switch 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 layout_switch 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 layout_switch. 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.
layout_switch is provided by the TradingView MCP Jackson MCP server (nimit791/tradingview-mcp-jackson). 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 →