ui_open_panel · Tradingview MCP: Risk & Policy

WHAT IT DOES

What ui_open_panel does on Tradingview

AI agents invoke ui_open_panel to trigger actions in Tradingview. 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 ui_open_panel needs a policy

This tool triggers UI actions in an external application (TradingView Desktop) via Chrome DevTools Protocol, manipulating the application's panel state. It doesn't just read data, but actively changes the UI state and can open panels like 'trading' or 'strategy-tester' which could lead to unintended interactions. It falls under Execute as it triggers external application operations whose effects depend on arguments.

From the tool's definition Open, close, or toggle TradingView panels (pine-editor, strategy-tester, watchlist, alerts, trading)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ui_open_panel Rate-limited

ui_open_panel 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": {
    "ui_open_panel": {
      "limits": [
        {
          "counter": "ui_open_panel_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, so you can run agents against it safely.

FAQ

Questions about ui_open_panel

What does the ui_open_panel tool do? +

Open, close, or toggle TradingView panels (pine-editor, strategy-tester, watchlist, alerts, trading). It is categorised as a Execute tool in the Tradingview MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ui_open_panel? +

Register the Tradingview MCP server in PolicyLayer and add a rule for ui_open_panel: 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. Nothing to install.

What risk level is ui_open_panel? +

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

Can I rate-limit ui_open_panel? +

Yes. Add a rate_limit block to the ui_open_panel 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 ui_open_panel completely? +

Set action: deny in the PolicyLayer policy for ui_open_panel. 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 ui_open_panel? +

ui_open_panel is provided by the Tradingview MCP server (lionfaion/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.