pine_check

THE RISK

High Risk

Compiling Pine Script is not a pure read operation; it triggers an external process (the TradingView compiler) via CDP. While it doesn't directly run the script on live charts, compilation is an Execute-category action with moderate blast radius — misuse could introduce malicious Pine Script or cause unexpected TradingView state changes.

From the tool's definition 'Compile Pine Script via TradingView' — compiling code triggers execution of an external operation (compilation pipeline) within the TradingView environment via Chrome DevTools Protocol

Documented attack patterns abuse exactly the kind of access pine_check gives an agent:

HOW TO CONTROL PINE_CHECK

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_check:

policy.json

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

pine_check 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.

Create a free account and register TradingView MCP Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More TradingView MCP Bridge tools

Destructive alert_delete Delete all alerts or open context menu for deletion Destructive draw_clear Remove all drawings from the chart Destructive draw_remove_one Remove a specific drawing by entity ID Execute batch_run Run an action across multiple symbols and/or timeframes Execute pine_compile Compile / add the current Pine Script to the chart Execute pine_smart_compile Intelligent compile: detects button, compiles, checks errors, reports study changes Execute replay_start Start bar replay mode, optionally at a specific date Execute replay_stop Stop replay and return to realtime

All 78 TradingView MCP Bridge tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in TradingView MCP Bridge → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the pine_check tool do? +

Compile Pine Script via TradingView\. 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_check? +

Register the TradingView MCP Bridge 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 Bridge. Nothing to install.

What risk level is pine_check? +

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

Can I rate-limit pine_check? +

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.

How do I block pine_check completely? +

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.

What MCP server provides pine_check? +

pine_check 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.

Enforce policy on every TradingView MCP Bridge tool call.

Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN TRADINGVIEW MCP BRIDGE →

Free to start. No card required.

78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT PINE_CHECK ON TRADINGVIEW MCP BRIDGE DOES

// THE RISK

// HOW TO CONTROL PINE_CHECK

// EXPLORE