Get current Pine Script source code from the editor
AI agents call pine_get_source to retrieve information from TradingView MCP Jackson without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool purely retrieves source code from the TradingView Pine Script editor without modifying, executing, or deleting anything. It has no side effects beyond data retrieval, fitting the 'Read' category. Severity is low because reading source code poses minimal security risk—the content is already accessible to users with editor access, and retrieval alone cannot harm systems or data.
From the tool's definition Tool name and description: 'Get current Pine Script source code from the editor' - this is a retrieval operation with no modification or execution of code, only reading/fetching existing source code.
Attacks that exploit this kind of access
Get current Pine Script source code from the editor. It is categorised as a Read tool in the TradingView MCP Jackson MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Jackson MCP server in PolicyLayer and add a rule for pine_get_source: 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 Jackson. Nothing to install.
pine_get_source 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_source 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_source. 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_source is provided by the TradingView MCP Jackson MCP server (nimit791/tradingview-mcp-jackson). 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 →