Run static analysis on Pine Script code WITHOUT compiling — catches array out-of-bounds, unguarded array.first()/last(), bad loop bounds, and implicit bool casts. Works offline, no TradingView connection needed.
AI agents invoke pine_analyze 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.
The tool executes a static analysis engine against Pine Script code. While it doesn't compile or deploy anything, it does 'run' analysis logic on user-supplied code. It has no side effects on external systems and works offline, limiting blast radius.
From the tool's definition 'Run static analysis on Pine Script code' — actively processes and analyzes code, executing analysis logic against provided scripts
Attacks that exploit this kind of access
Run static analysis on Pine Script code WITHOUT compiling — catches array out-of-bounds, unguarded array.first()/last(), bad loop bounds, and implicit bool casts. Works offline, no TradingView connection needed. 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_analyze: 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_analyze 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_analyze 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_analyze. 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_analyze 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 →