Compile / add the current Pine Script to the chart
AI agents invoke pine_compile to trigger actions in TradingView MCP Jackson. 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 user-provided or existing Pine Script code in a live trading context. Pine Script is a domain-specific programming language for TradingView indicators and strategies. Executing arbitrary Pine Script can modify chart state, trigger alerts, execute trading logic, or produce unintended financial market interactions.
From the tool's definition "Compile / add the current Pine Script to the chart" - this tool executes Pine Script code by compiling and adding it to a live trading chart, which triggers code execution in the TradingView environment.
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 Jackson MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Jackson 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 Jackson. 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 Jackson MCP server (nimit791/tradingview-mcp-jackson). 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 →