layout_switch · Tradingview MCP: Risk & Policy

WHAT IT DOES

What layout_switch does on Tradingview

AI agents invoke layout_switch to trigger actions in Tradingview. 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 layout_switch needs a policy

Switching to a layout triggers an external operation in the TradingView Desktop app via Chrome DevTools Protocol, changing the application's active state. It is not merely reading data, nor creating/modifying stored data reversibly in the traditional sense — it executes a UI/application action. Misuse could disrupt a user's active workflow or analysis session, but has limited blast radius beyond the local app state.

From the tool's definition Switch to a saved chart layout by name or ID

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tradingview, so you can run agents against it safely.

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, 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 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. 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 (lionfaion/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

layout_switch is one line of Tradingview'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 →