Compile / add the current Pine Script to the chart
AI agents invoke pine_compile 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.
Compiling and adding Pine Script to a chart constitutes code execution with side effects that depend on the script's logic. While not destructive in the file-deletion sense, a malicious or incorrect Pine Script could manipulate charts, trigger alerts, execute trades via strategies, or consume resources. The blast radius is significant in a financial context where TradingView is used for trading decisions.
From the tool's definition Tool description states 'Compile / add the current Pine Script to the chart' — this compiles and executes arbitrary Pine Script code against a live charting application.
Attacks that exploit this kind of access
Compile / add the current Pine Script to the chart. 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 pine_compile: 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.
pine_compile 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 pine_compile 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 pine_compile. 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.
pine_compile 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 →