tab_new · TradingView MCP: Risk & Policy

WHAT IT DOES

What tab_new does on TradingView MCP

AI agents invoke tab_new to trigger actions in TradingView MCP. 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 tab_new needs a policy

Categorized as Execute rather than Write because it triggers an action in an external application (TradingView Desktop) via browser automation. While not inherently destructive or financial, it performs an operation beyond simple data retrieval. Severity is medium because an agent could be manipulated to open tabs as part of a chain leading to unintended trading actions, though the immediate risk is limited.

From the tool's definition Tool opens a new chart tab via automated control of TradingView Desktop through Chrome DevTools Protocol. Opening UI elements is a form of execution that triggers external operations (tab creation) whose side effects depend on subsequent actions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

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