High Risk →

layout_switch

Switch to a saved chart layout by name or ID

How to control layout_switch ↓

AI agents invoke layout_switch 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.

High Risk

This tool triggers an external operation in the TradingView Desktop application — switching the active chart layout. It doesn't merely read data or write/create a record; it executes a UI/application state change via Chrome DevTools Protocol. Misuse could disrupt a user's active workflow or analysis session, though it is reversible by switching back.

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

Documented attack patterns abuse exactly the kind of access layout_switch 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 layout_switch:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "layout_switch": {
      "limits": [
        {
          "counter": "layout_switch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register TradingView MCP Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

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 Bridge 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 Bridge 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 Bridge. 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 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.

Enforce policy on every TradingView MCP Bridge tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.