coin_analysis
AI agents call coin_analysis 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 analyze cryptocurrency/stock data and return insights. Without an explicit description, confidence is moderate, but the server's stated purpose (analysis, screening, pattern recognition) and all sibling tools being read-only analytics strongly suggest this is a Read operation that retrieves or queries market data without side effects.
From the tool's definition Tool named 'coin_analysis' belongs to a server for 'market analysis' and 'trading intelligence through natural language queries'. Sibling tools are all analytical in nature (pattern, scan, rating, volume analysis, gainers/losers).
Attacks that exploit this kind of access
coin_analysis. 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 coin_analysis: 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.
coin_analysis 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 coin_analysis 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 coin_analysis. 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.
coin_analysis is provided by the TradingView MCP Server MCP server (patch-ridermg48/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 →