AI agents invoke convert_pine_version 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.
Based on the server description mentioning 'version conversion' for Pine Script, this tool likely transforms/converts Pine Script code from one version to another. This is a Write/Execute operation as it modifies or rewrites code. With an empty description, confidence is lowered. Given the context of code transformation, Execute is most appropriate as it processes and rewrites script content.
From the tool's definition Tool name: convert_pine_version; description is empty. Server context mentions 'version conversion' as part of Pine Script v6 development tools.
Documented attack patterns abuse exactly the kind of access convert_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 convert_pine_version:
{
"version": "1",
"default": "deny",
"tools": {
"convert_pine_version": {
"limits": [
{
"counter": "convert_pine_version_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}convert_pine_version 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.
convert_pine_version. 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 convert_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.
convert_pine_version 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 convert_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 convert_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.
convert_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.