pine_get_errors

Get Pine Script compilation errors from Monaco markers

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debarpan2000-tradingview-mcp/pine-get-errors.md

WHAT IT DOES

What pine_get_errors does on TradingView MCP Server

AI agents call pine_get_errors to retrieve information from TradingView MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pine_get_errors is rated Low

This tool retrieves and queries compilation error information from the Pine Script editor's Monaco markers. It performs no state changes, does not execute code, and returns read-only diagnostic data. While the broader server context involves trading and chart analysis, this specific tool is purely informational, making it a Read-category tool with low severity.

From the tool's definition Tool name 'pine_get_errors' and description 'Get Pine Script compilation errors from Monaco markers' indicate retrieval of diagnostic information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pine_get_errors safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pine_get_errors, this is the rule to start with:

pine_get_errors Allowed

pine_get_errors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pine_get_errors": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every pine_get_errors call is checked against it from then on.

FAQ

Questions about pine_get_errors

What does the pine_get_errors tool do? +

Get Pine Script compilation errors from Monaco markers. It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pine_get_errors? +

Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for pine_get_errors: 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 Server. Nothing to install.

What risk level is pine_get_errors? +

pine_get_errors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pine_get_errors? +

Yes. Add a rate_limit block to the pine_get_errors 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_get_errors completely? +

Set action: deny in the PolicyLayer policy for pine_get_errors. 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_get_errors? +

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

KEEP EXPLORING

More on TradingView MCP Server, and thousands of servers like it.

This server

All 78 TradingView MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →