pine_check · TradingView MCP Bridge MCP: Risk & Policy

WHAT IT DOES

What pine_check does on TradingView MCP Bridge

AI agents invoke pine_check 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_check needs a policy

Compiling Pine Script is an execution-class action: it sends code to TradingView and triggers a compilation process via the Chrome DevTools Protocol. While it doesn't directly delete data or move money, it executes an external operation whose effects depend on the script content provided, placing it in the Execute category. Misuse could involve compiling malicious or resource-intensive scripts.

From the tool's definition 'Compile Pine Script via TradingView' — compiling code triggers an external operation (compilation) on TradingView Desktop via Chrome DevTools Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pine_check Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pine_check": {
      "limits": [
        {
          "counter": "pine_check_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_check

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 (thinhbv/tradingview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.