AI agents use pine_new to create or update resources in TradingView MCP Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP Bridge environment.
This tool creates a new Pine Script document in TradingView. It is a Write operation as it creates new data/content. It is reversible (the script can be deleted). Severity is medium because creating scripts in a trading platform could be used to set up automated trading logic, but the act of creation itself doesn't execute trades or irreversibly destroy data.
From the tool's definition Create a new blank Pine Script
Documented attack patterns abuse exactly the kind of access pine_new 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_new:
{
"version": "1",
"default": "deny",
"tools": {
"pine_new": {
"limits": [
{
"counter": "pine_new_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pine_new 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.
Free to start. No card required.
Create a new blank Pine Script. It is categorised as a Write tool in the TradingView MCP Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for pine_new: 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_new 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_new 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_new. 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_new 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.