Set Pine Script source code in the editor
AI agents use pine_set_source to create or update resources in TradingView MCP Jackson — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP Jackson environment.
This tool creates or modifies Pine Script source code within TradingView's editor. While reversible (code can be overwritten again), it affects live trading logic if deployed. Misuse could cause an AI to inject malicious or broken scripts into active trading workflows, leading to incorrect technical analysis or unintended trade signals.
From the tool's definition Tool description explicitly states 'Set Pine Script source code' — this modifies code in the editor. The term 'set' indicates data modification rather than retrieval or deletion.
Attacks that exploit this kind of access
Set Pine Script source code in the editor. It is categorised as a Write tool in the TradingView MCP Jackson MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TradingView MCP Jackson MCP server in PolicyLayer and add a rule for pine_set_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_set_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pine_set_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_set_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_set_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 →