tab_switch
Switch to a chart tab by index
This record as markdown: /tools/byeung888-tradingview-mcp/tab-switch.md
What tab_switch does on TradingView MCP Bridge
AI agents invoke tab_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.
Why tab_switch is rated High
This tool performs a browser/application UI action (switching tabs) rather than simply reading data or writing persistent data. It executes an external operation in the locally running TradingView app. Misuse could disrupt the user's workflow by switching away from their active chart, but has limited blast radius beyond UI disruption.
From the tool's definition Switch to a chart tab by index — triggers a UI navigation action in the TradingView Desktop app via Chrome DevTools Protocol
Attacks that exploit this kind of access
The rule that runs tab_switch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tab_switch, this is the rule to start with:
tab_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.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every tab_switch call is checked against it from then on.
Questions about tab_switch
Switch to a chart tab by index. 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.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for tab_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.
tab_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 tab_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 tab_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.
tab_switch is provided by the TradingView MCP Bridge MCP server (byeung888/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TradingView MCP Bridge, and thousands of servers like it.
Across the catalogue