AI agents call detect_pine_version to retrieve information from TradingView MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to identify or retrieve the version of a Pine Script without modifying, executing, or deleting anything. It likely inspects code metadata. Confidence is moderate (0.7) rather than high because the description is empty; however, the name and surrounding read-only analysis tools strongly suggest this is a query/detection operation with no side effects.
From the tool's definition Tool name 'detect_pine_version' suggests detection/inspection of Pine Script version; sibling tools like 'explain_pine_error', 'convert_pine_version', and 'get_adx' are all read-only technical analysis and code inspection utilities.
Documented attack patterns abuse exactly the kind of access detect_pine_version 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 detect_pine_version:
{
"version": "1",
"default": "deny",
"tools": {
"detect_pine_version": {}
}
}detect_pine_version is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
detect_pine_version. It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for detect_pine_version: 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.
detect_pine_version is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the detect_pine_version 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 detect_pine_version. 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.
detect_pine_version 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.