smart_volume_scanner
AI agents call smart_volume_scanner 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.
Based on the server's stated purpose (advanced cryptocurrency/stock market analysis with screening and indicators) and the pattern of sibling tools (all scanners and analyzers), 'smart_volume_scanner' is almost certainly a read-only market data analysis tool that retrieves and analyzes volume metrics without side effects.
From the tool's definition Tool name 'smart_volume_scanner' indicates scanning/analysis functionality. Sibling tools on this server (bollinger_scan, consecutive_candles_scan, volume_breakout_scanner, volume_confirmation_analysis) are all read-only market analysis and screening…
Attacks that exploit this kind of access
smart_volume_scanner. 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 smart_volume_scanner: 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.
smart_volume_scanner 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 smart_volume_scanner 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 smart_volume_scanner. 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.
smart_volume_scanner 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 →