pine_compile
Compile / add the current Pine Script to the chart
This record as markdown: /tools/byeung888-tradingview-mcp/pine-compile.md
What pine_compile does on TradingView MCP Bridge
AI agents invoke pine_compile to trigger actions in TradingView MCP Bridge. 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_compile is rated High
Compiling and adding Pine Script to a chart executes code in the TradingView environment. While not destructive on its own, the executed Pine Script can perform arbitrary financial analysis, generate signals, or trigger trading-related workflows.
From the tool's definition Tool description states 'Compile / add the current Pine Script to the chart' — this compiles and executes Pine Script code against the chart, triggering external operations whose effects depend on the script's logic and content.
Attacks that exploit this kind of access
The rule that runs pine_compile 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_compile, this is the rule to start with:
pine_compile 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 Bridge, apply this rule, and every pine_compile call is checked against it from then on.
Questions about pine_compile
Compile / add the current Pine Script to the chart. It is categorised as a Execute tool in the TradingView MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Bridge 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 MCP Bridge. 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 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.
Across the catalogue