This record as markdown: /tools/byeung888-tradingview-mcp/tab-new.md
What tab_new does on TradingView MCP Bridge
AI agents invoke tab_new 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_new is rated High
Opening a new chart tab is an executable action that modifies the state of the TradingView application. While not destructive or financial in itself, it represents execution of a command in an external system. The tool sits among other chart manipulation and automation tools in a trading context where unintended tab creation could disrupt workflows.
From the tool's definition Tool name 'tab_new' and description 'Open a new chart tab' indicate triggering an action (opening a new tab) in an external application (TradingView Desktop) via Chrome DevTools Protocol.
Attacks that exploit this kind of access
The rule that runs tab_new 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_new, this is the rule to start with:
tab_new 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_new call is checked against it from then on.
Questions about tab_new
Open a new chart tab. 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_new: 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_new 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_new 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_new. 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_new 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