AI agents invoke test_pine_script to trigger actions in TradingView MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name strongly implies running/executing Pine Script code for testing purposes. In the context of a Pine Script development environment, 'test' typically means executing the script to validate its behavior. Since the description is empty, confidence is reduced, but the sibling tools (validate, autocomplete, convert) and the server's emphasis on Pine Script development suggest this tool executes script code.
From the tool's definition Tool name 'test_pine_script' and server context involving Pine Script v6 development tools including syntax validation and execution capabilities
Documented attack patterns abuse exactly the kind of access test_pine_script gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_pine_script:
{
"version": "1",
"default": "deny",
"tools": {
"test_pine_script": {
"limits": [
{
"counter": "test_pine_script_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}test_pine_script stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
test_pine_script. It is categorised as a Execute tool in the TradingView MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for test_pine_script: 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.
test_pine_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_pine_script 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 test_pine_script. 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.
test_pine_script is provided by the TradingView MCP Server MCP server (lev-corrupted/tradingviewmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TradingView MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 TradingView MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.