pine_analyze
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.
This record as markdown: /tools/debarpan2000-tradingview-mcp/pine-analyze.md
What pine_analyze does on TradingView MCP Server
AI agents invoke pine_analyze to trigger actions in TradingView MCP Server. 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 pine_analyze is rated High
Although the tool doesn't compile or deploy code and needs no TradingView connection, it still executes a non-trivial analysis engine against arbitrary user-supplied code. It has no write or destructive side effects, but it is more than a passive read — it runs logic (array bounds checks, loop analysis, implicit cast detection) on the input.
From the tool's definition 'Run static analysis on Pine Script code WITHOUT compiling' — the tool actively executes analysis logic (parsing, AST traversal, rule checks) against arbitrary Pine Script code provided as input
Attacks that exploit this kind of access
The rule that runs pine_analyze safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pine_analyze, this is the rule to start with:
pine_analyze 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 Server, apply this rule, and every pine_analyze call is checked against it from then on.
Questions about pine_analyze
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 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Server 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 MCP Server. 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 MCP server (debarpan2000/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 Server, and thousands of servers like it.
Across the catalogue