volume_breakout_scanner
AI agents call volume_breakout_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.
The tool appears to scan and retrieve volume breakout data from TradingView for analysis purposes, consistent with the server's stated function of 'real-time screening, technical indicators, and pattern recognition.' The absence of a description prevents full certainty, but contextual evidence from sibling tools and naming conventions strongly suggest this is a Read operation that queries market data without side…
From the tool's definition Tool name 'volume_breakout_scanner' indicates retrieval of market data through scanning functionality. Sibling tools on this server (bollinger_scan, consecutive_candles_scan, smart_volume_scanner, top_gainers, top_losers) are all read-only analysis and…
Attacks that exploit this kind of access
volume_breakout_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 volume_breakout_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.
volume_breakout_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 volume_breakout_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 volume_breakout_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.
volume_breakout_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 →