Compile Pine Script via TradingView\
AI agents invoke pine_check 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.
Compiling Pine Script requires executing code through TradingView's compiler. While it may not directly modify chart state, it triggers an external operation (compilation) via CDP, which qualifies as Execute. Misuse could involve injecting malicious Pine Script for compilation or probing TradingView internals.
From the tool's definition 'Compile Pine Script via TradingView' — compiling code is an execution operation that runs/processes scripts through TradingView's compiler engine via Chrome DevTools Protocol
Attacks that exploit this kind of access
Compile Pine Script via TradingView\. 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_check: 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_check 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_check 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_check. 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_check 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 →