pine_smart_compile · Tradingview MCP: Risk & Policy

WHAT IT DOES

What pine_smart_compile does on Tradingview

AI agents invoke pine_smart_compile to trigger actions in Tradingview. 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 IT NEEDS A POLICY

Why pine_smart_compile needs a policy

Compiling Pine Script is an Execute action—it runs code through TradingView's compiler and triggers external operations (button detection, compilation, error checking) whose effects depend on the script arguments being compiled. While not destructive by itself (compilation doesn't delete data), it is a form of code execution.

From the tool's definition Tool "compiles" Pine Script code and "checks errors" via TradingView Desktop automation. The description confirms it detects UI buttons and performs compilation, which are code execution operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pine_smart_compile Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pine_smart_compile": {
      "limits": [
        {
          "counter": "pine_smart_compile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tradingview, so you can run agents against it safely.

FAQ

Questions about pine_smart_compile

What does the pine_smart_compile tool do? +

Intelligent compile: detects button, compiles, checks errors, reports study changes. It is categorised as a Execute tool in the Tradingview MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pine_smart_compile? +

Register the Tradingview 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. Nothing to install.

What risk level is pine_smart_compile? +

pine_smart_compile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pine_smart_compile? +

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.

How do I block pine_smart_compile completely? +

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.

What MCP server provides pine_smart_compile? +

pine_smart_compile is provided by the Tradingview MCP server (lionfaion/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.