ui_open_panel
Open, close, or toggle TradingView panels (pine-editor, strategy-tester, watchlist, alerts, trading)
This record as markdown: /tools/byeung888-tradingview-mcp/ui-open-panel.md
What ui_open_panel does on TradingView MCP Bridge
AI agents invoke ui_open_panel 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 ui_open_panel is rated High
This tool manipulates the TradingView desktop application's UI by opening, closing, or toggling panels. It triggers external operations in a running application via CDP, making it an Execute-category tool. Misuse could disrupt a user's active workflow or expose unintended panels (e.g., trading panel), but no direct financial transactions or data destruction occurs.
From the tool's definition 'Open, close, or toggle TradingView panels' — triggers UI actions in an external application via Chrome DevTools Protocol
Attacks that exploit this kind of access
The rule that runs ui_open_panel 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 ui_open_panel, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every ui_open_panel call is checked against it from then on.
Questions about ui_open_panel
Open, close, or toggle TradingView panels (pine-editor, strategy-tester, watchlist, alerts, trading). 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 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 MCP Bridge. Nothing to install.
ui_open_panel 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 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.
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.
ui_open_panel 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