tv_launch
Launch TradingView Desktop with Chrome DevTools Protocol (remote debugging) enabled. Auto-detects install location on Mac, Windows, and Linux.
This record as markdown: /tools/byeung888-tradingview-mcp/tv-launch.md
What tv_launch does on TradingView MCP Bridge
AI agents invoke tv_launch 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 tv_launch is rated High
The tool launches an application and explicitly enables remote debugging (CDP), which is a protocol that allows arbitrary code execution against the running process. This goes beyond simple data retrieval or modification—it establishes an execution gateway.
From the tool's definition Launches TradingView Desktop with Chrome DevTools Protocol (remote debugging) enabled, which enables execution of arbitrary code and commands against the TradingView process. Remote debugging via CDP is an execution interface.
Attacks that exploit this kind of access
The rule that runs tv_launch 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 tv_launch, this is the rule to start with:
tv_launch 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 tv_launch call is checked against it from then on.
Questions about tv_launch
Launch TradingView Desktop with Chrome DevTools Protocol (remote debugging) enabled. Auto-detects install location on Mac, Windows, and Linux. 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 tv_launch: 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.
tv_launch 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 tv_launch 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 tv_launch. 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.
tv_launch 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