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 only retrieves and reads existing console/log data from the Pine Script environment. It performs no writes, deletions, code execution, or external operations. The data retrieved is informational (compile messages, logs, errors) used for debugging and analysis. There is no risk of data modification, financial impact, or destructive action.
From the tool's definition Tool name 'pine_get_console' and description explicitly states it 'Read[s] Pine Script console/log output (compile messages, log.info(), errors)' — a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access pine_get_console gives an agent:
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_get_console:
{
"version": "1",
"default": "deny",
"tools": {
"pine_get_console": {}
}
}pine_get_console is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.