consecutive_candles_scan
AI agents call consecutive_candles_scan 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.
This tool appears to scan and analyze consecutive candlestick patterns to identify market conditions or trading signals. Like its sibling analysis tools, it retrieves and analyzes market data without modifying it, executing trades, or causing financial transactions.
From the tool's definition Tool name 'consecutive_candles_scan' indicates analysis of candlestick patterns in market data. Empty description, but sibling tools (advanced_candle_pattern, bollinger_scan, coin_analysis, smart_volume_scanner, top_gainers, top_losers,…
Attacks that exploit this kind of access
consecutive_candles_scan. 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 consecutive_candles_scan: 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.
consecutive_candles_scan 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 consecutive_candles_scan 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 consecutive_candles_scan. 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.
consecutive_candles_scan 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 →