AI agents call get_pine_documentation 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.
This tool retrieves static documentation—a read operation with no side effects. Even if the description is empty, the name strongly implies a documentation lookup utility. The low severity reflects that documentation access poses minimal risk; an agent cannot cause harm by reading API or language reference materials.
From the tool's definition Tool name 'get_pine_documentation' with empty description suggests retrieval of reference documentation for Pine Script v6.
Documented attack patterns abuse exactly the kind of access get_pine_documentation 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 get_pine_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_pine_documentation": {}
}
}get_pine_documentation 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.
get_pine_documentation. 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 get_pine_documentation: 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.
get_pine_documentation 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 get_pine_documentation 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 get_pine_documentation. 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.
get_pine_documentation 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.