Compile / add the current Pine Script to the chart
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.
This tool executes user-provided or modified Pine Script code within TradingView's environment. Although Pine Script execution on charts itself is sandboxed, the tool can trigger script validation errors, cause resource consumption, or introduce unintended financial signals/alerts. The consequences depend on what the Pine Script contains—it could compute malicious trading signals or drain system resources.
From the tool's definition Tool description states it will "Compile / add the current Pine Script to the chart." Pine Script is executable code. Compiling and adding it to the chart means executing custom trading logic in a live financial charting system.
Documented attack patterns abuse exactly the kind of access pine_compile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for pine_compile:
{
"version": "1",
"default": "deny",
"tools": {
"pine_compile": {
"limits": [
{
"counter": "pine_compile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.