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/byeung888-tradingview-mcp/pine-analyze.md
What pine_analyze does on TradingView MCP Bridge
AI agents call pine_analyze to retrieve information from TradingView MCP Bridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pine_analyze is rated Low
This tool retrieves and analyzes code structure without executing it, modifying data, or triggering any external operations. Static analysis is purely informational and non-destructive. Even in a misuse scenario, an AI agent cannot cause harm through analysis alone — the worst outcome is false positives/negatives in error detection, which is low severity.
From the tool's definition Tool performs 'static analysis' on code 'WITHOUT compiling' — it examines Pine Script for errors without executing it or modifying any data.
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 Bridge, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, 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 Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Bridge 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 Bridge. Nothing to install.
pine_analyze is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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 Bridge MCP server (byeung888/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 Bridge, and thousands of servers like it.
This server
Across the catalogue