pine_save

Save the current Pine Script (Ctrl+S)

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debarpan2000-tradingview-mcp/pine-save.md

WHAT IT DOES

What pine_save does on TradingView MCP Server

AI agents use pine_save to create or update resources in TradingView MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP Server environment.

RISK

Why pine_save is rated Medium

The tool saves Pine Script code, which is a write operation that persists data modifications. It is reversible (can be edited/undone later) and does not delete data irreversibly. While saved scripts could theoretically be deployed to affect trading, the save operation itself is confined to modifying the script artifact.

From the tool's definition Tool description explicitly states 'Save the current Pine Script', which creates or modifies data (the script file) reversibly through a standard save operation (Ctrl+S).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pine_save safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pine_save, this is the rule to start with:

pine_save Rate-limited

pine_save stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pine_save": {
      "limits": [
        {
          "counter": "pine_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every pine_save call is checked against it from then on.

FAQ

Questions about pine_save

What does the pine_save tool do? +

Save the current Pine Script (Ctrl+S). It is categorised as a Write tool in the TradingView MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pine_save? +

Register the TradingView MCP Server 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 Server. Nothing to install.

What risk level is pine_save? +

pine_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pine_save? +

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.

How do I block pine_save completely? +

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.

What MCP server provides pine_save? +

pine_save is provided by the TradingView MCP Server MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Server, and thousands of servers like it.

This server

All 78 TradingView MCP Server tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →