Change the chart symbol
AI agents invoke chart_set_symbol 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 interacts with an external application (TradingView Desktop) through Chrome DevTools Protocol to modify the active chart's symbol. It is not a simple data write within a database, but rather an action that drives UI/state changes in an external running process, making it Execute. Misuse could cause unintended chart navigation or disrupt active trading analysis workflows.
From the tool's definition 'Change the chart symbol' — triggers an external operation on the locally running TradingView Desktop app via Chrome DevTools Protocol
Attacks that exploit this kind of access
Change the chart symbol. 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 chart_set_symbol: 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.
chart_set_symbol 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 chart_set_symbol 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 chart_set_symbol. 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.
chart_set_symbol 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 →