consecutive_candles_scan
AI agents call consecutive_candles_scan 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.
The tool appears to be a technical analysis scanner that queries/analyzes consecutive candlestick patterns from market data. It likely returns analysis results without executing trades, modifying data, or moving money. The '_scan' suffix and sibling tools like 'bollinger_scan' and 'advanced_candle_pattern' confirm this is a read-only analytical function.
From the tool's definition Tool name 'consecutive_candles_scan' suggests scanning/analyzing candlestick patterns in financial data. The description is empty, but the naming convention and context (trading analysis toolkit with technical analysis tools) indicates data retrieval and…
Attacks that exploit this kind of access
consecutive_candles_scan. 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 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. 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 (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 →