layout_switch

Switch to a saved chart layout by name or ID

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debarpan2000-tradingview-mcp/layout-switch.md

WHAT IT DOES

What layout_switch does on TradingView MCP Server

AI agents invoke layout_switch to trigger actions in TradingView MCP Server. 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.

RISK

Why layout_switch is rated High

This tool triggers an external operation in the TradingView Desktop application, changing the active chart layout. It is not a simple read (it changes application state) nor a write to stored data, but rather an execution of an application action via CDP. Misuse could disrupt a user's active workflow or analysis session, but it is reversible by switching back, keeping severity at medium.

From the tool's definition 'Switch to a saved chart layout by name or ID' — triggers a UI/application state change in TradingView Desktop via Chrome DevTools Protocol

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs layout_switch safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For layout_switch, this is the rule to start with:

layout_switch Rate-limited

layout_switch 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": {
    "layout_switch": {
      "limits": [
        {
          "counter": "layout_switch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every layout_switch call is checked against it from then on.

FAQ

Questions about layout_switch

What does the layout_switch tool do? +

Switch to a saved chart layout by name or ID. It is categorised as a Execute tool in the TradingView MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on layout_switch? +

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

What risk level is layout_switch? +

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

Can I rate-limit layout_switch? +

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.

How do I block layout_switch completely? +

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.

What MCP server provides layout_switch? +

layout_switch is provided by the TradingView MCP Server MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Server, and thousands of servers like it.

This server

All 78 TradingView MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →