tab_new

Open a new chart tab

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/tab-new.md

WHAT IT DOES

What tab_new does on TradingView MCP Server

AI agents invoke tab_new 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 tab_new is rated High

The tool executes a browser/application action (opening a new tab) whose consequences depend on context and subsequent operations. While not destructive or financial in isolation, it is an Execute-class tool because it triggers external operations in TradingView Desktop.

From the tool's definition "Open a new chart tab" - creates a new UI element and triggers browser/application state changes via Chrome DevTools Protocol automation. This is an observable side effect that modifies the application state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tab_new 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 tab_new, this is the rule to start with:

tab_new Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tab_new": {
      "limits": [
        {
          "counter": "tab_new_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 tab_new call is checked against it from then on.

FAQ

Questions about tab_new

What does the tab_new tool do? +

Open a new chart tab. 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 tab_new? +

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

What risk level is tab_new? +

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

Can I rate-limit tab_new? +

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.

How do I block tab_new completely? +

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.

What MCP server provides tab_new? +

tab_new 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 →