Launch TradingView Desktop with Chrome DevTools Protocol (remote debugging) enabled. Auto-detects install location on Mac, Windows, and Linux.
AI agents invoke tv_launch 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.
This tool executes an external application (TradingView Desktop) and enables Chrome DevTools Protocol debugging. This is an Execute category action because it triggers external operations and establishes a remote debugging interface whose effects depend on what commands are subsequently sent to it.
From the tool's definition "Launch TradingView Desktop with Chrome DevTools Protocol (remote debugging) enabled" - directly launches an application and enables remote debugging capabilities, which allows execution of arbitrary operations on the running process.
Attacks that exploit this kind of access
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 Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tradingview 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. 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 server (lionfaion/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →