volume_breakout_scanner
AI agents call volume_breakout_scanner 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.
Based on the tool name and the pattern of sibling tools (all analysis/scan operations), this appears to be a read-only market data scanner that identifies volume breakout opportunities. It queries or filters existing financial data without modifying, executing external code, or moving money. The empty description reduces confidence slightly, but the scanning/analysis context strongly suggests a Read classification.
From the tool's definition Tool name 'volume_breakout_scanner' suggests scanning/querying market data for volume breakout patterns. Sister tools on the server (bollinger_scan, consecutive_candles_scan, egx_index_analysis) are all read-oriented market analysis tools.
Attacks that exploit this kind of access
volume_breakout_scanner. 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 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. 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 (mrxjeus-cpu/trading-mcp-bot). 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 →