Read Pine Script console/log output (compile messages, log.info(), errors)
AI agents call pine_get_console to retrieve information from TradingView MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries logging/console data from Pine Script execution without any side effects. It is purely informational and diagnostic in nature, fitting the Read category definition of retrieving data with no side effects. Severity is low because console output access poses minimal security risk and does not affect trading, market data, or system state.
From the tool's definition Tool name contains 'get' and description states 'Read Pine Script console/log output' with examples of read-only operations (compile messages, log.info(), errors). No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
Read Pine Script console/log output (compile messages, log.info(), errors). It is categorised as a Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for pine_get_console: 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.
pine_get_console 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_console 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_console. 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_console 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.
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 →