Save the current Pine Script (Ctrl+S)
AI agents use pine_save to create or update resources in TradingView MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP environment.
This tool creates or modifies data reversibly by saving Pine Script code to storage. While saving itself is not destructive, it writes/persists changes to a script resource. The severity is medium because misuse could overwrite legitimate trading scripts or introduce malicious Pine Script logic, but the effect is reversible (prior versions may exist, scripts can be edited or restored).
From the tool's definition pine_save performs a save operation (Ctrl+S) on Pine Script code. The description indicates it modifies/persists the current Pine Script.
Attacks that exploit this kind of access
Save the current Pine Script (Ctrl+S). It is categorised as a Write tool in the TradingView MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TradingView MCP server in PolicyLayer and add a rule for pine_save: 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. Nothing to install.
pine_save 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_save 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_save. 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_save is provided by the TradingView MCP server (ulianbass/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 →