FAST PATH for scalping / market-order setups. Returns quote, OHLCV summary, indicator values, chart context (including last_index for draw_position), AND open positions + pending orders — all in ONE round-trip over CDP (~50-150ms vs the ~1500ms it takes to call chart_get_state + quote_get + data_...
AI agents call trade_snapshot to retrieve information from TradingView MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
trade_snapshot retrieves market data, indicator state, and account information in a single query. While it accesses sensitive trading state (positions, orders), it performs no write, execute, or destructive operations.
From the tool's definition Tool description states it 'Returns quote, OHLCV summary, indicator values, chart context... AND open positions + pending orders' — purely retrieving and aggregating data with no modification, creation, or deletion of positions/orders.
Attacks that exploit this kind of access
FAST PATH for scalping / market-order setups. Returns quote, OHLCV summary, indicator values, chart context (including last_index for draw_position), AND open positions + pending orders — all in ONE round-trip over CDP (~50-150ms vs the ~1500ms it takes to call chart_get_state + quote_get + data_get_ohlcv + data_get_study_values + trading_get_positions + trading_get_orders sequentially). Auto-opens the Account Manager panel if it. It is categorised as a Read tool in the TradingView MCP MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP server in PolicyLayer and add a rule for trade_snapshot: 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. Nothing to install.
trade_snapshot 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 trade_snapshot 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 trade_snapshot. 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.
trade_snapshot is provided by the TradingView MCP server (ulianbass/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 →