Get Pine Script compilation errors from Monaco markers
AI agents call pine_get_errors to retrieve information from Tradingview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information (compilation errors) from the Monaco editor's marker system. It performs a read-only query of the current editor state to surface error messages to the user. There is no modification, execution, deletion, or financial impact. The blast radius of misuse is negligible—at worst, an agent could repeatedly call this to retrieve already-computed errors, causing minimal harm.
From the tool's definition Tool name 'pine_get_errors' combined with description 'Get Pine Script compilation errors from Monaco markers' indicates data retrieval with no side effects. The action is to fetch and display existing error information from the editor state.
Attacks that exploit this kind of access
Get Pine Script compilation errors from Monaco markers. It is categorised as a Read tool in the Tradingview MCP Server, which means it retrieves data without modifying state.
Register the Tradingview 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. Nothing to install.
pine_get_errors is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
pine_get_errors 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →