Report which known TradingView API paths are available and their methods
AI agents call tv_discover to retrieve information from Tradingview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs passive reconnaissance of API paths and methods. It returns informational data about what APIs exist and their capabilities, with no side effects, state changes, code execution, or data modification. This is a classic Read operation with minimal blast radius—knowledge of available endpoints alone cannot cause harm without subsequent misuse of those endpoints through other tools.
From the tool's definition Tool name 'tv_discover' and description 'Report which known TradingView API paths are available and their methods' indicate a discovery/enumeration function that retrieves information about available API endpoints without modifying any data.
Attacks that exploit this kind of access
Report which known TradingView API paths are available and their methods. It is categorised as a Read tool in the Tradingview MCP Server, which means it retrieves data without modifying state.
Register the Tradingview MCP server in PolicyLayer and add a rule for tv_discover: 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. Nothing to install.
tv_discover 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 tv_discover 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 tv_discover. 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.
tv_discover is provided by the Tradingview MCP server (lionfaion/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →