pine_compile · TradingView MCP Bridge MCP: Risk & Policy

WHAT IT DOES

What pine_compile does on TradingView MCP Bridge

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.

WHY IT NEEDS A POLICY

Why pine_compile needs a policy

This is Execute rather than Write because compiling and deploying a Pine Script to a chart triggers active code execution in a financial trading platform, not merely data modification. The tool can cause automated trading actions, strategy backtests, or alert generation depending on script logic.

From the tool's definition Tool compiles and adds Pine Script code to TradingView charts. Pine Script is executable code that runs within TradingView's environment and can trigger automated trading strategies, alerts, and real-time market analysis.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pine_compile Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pine_compile": {
      "limits": [
        {
          "counter": "pine_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 MCP Bridge, so you can run agents against it safely.

FAQ

Questions about pine_compile

What does the pine_compile tool do? +

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.

How do I enforce a policy on pine_compile? +

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.

What risk level is pine_compile? +

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

Can I rate-limit pine_compile? +

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.

How do I block pine_compile completely? +

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.

What MCP server provides pine_compile? +

pine_compile is provided by the TradingView MCP Bridge MCP server (thinhbv/tradingview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.