Intelligent compile: detects button, compiles, checks errors, reports study changes
AI agents invoke pine_smart_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 Pine Script compilation, which is a code execution operation. While compilation itself is not inherently destructive, it triggers external processes and can produce side effects (indicator changes, study modifications) depending on the script content.
From the tool's definition Tool description states it "detects button, compiles, checks errors" — this indicates execution of Pine Script compilation logic, which runs code transformation and analysis operations.
Documented attack patterns abuse exactly the kind of access pine_smart_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_smart_compile:
{
"version": "1",
"default": "deny",
"tools": {
"pine_smart_compile": {
"limits": [
{
"counter": "pine_smart_compile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pine_smart_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.
Intelligent compile: detects button, compiles, checks errors, reports study changes. 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_smart_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_smart_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_smart_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_smart_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_smart_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.