Zonas de liquidación acumuladas cerca del precio actual de BTC (basado en forceOrders de Binance).
AI agents call trader_heatmap 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.
This tool retrieves and displays liquidation zone data from Binance for analytical purposes. It performs a read-only query of existing market data to visualize liquidation zones on a heatmap. There are no mutations, deletions, trade executions, or external side effects beyond fetching and displaying data. The low severity reflects that misuse (e.g., querying repetitively) poses minimal risk.
From the tool's definition The tool description indicates it 'zonas de liquidación acumuladas' (accumulated liquidation zones) 'cerca del precio actual de BTC' (near current BTC price) 'basado en forceOrders de Binance' (based on Binance force orders).
Attacks that exploit this kind of access
Zonas de liquidación acumuladas cerca del precio actual de BTC (basado en forceOrders de Binance). 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 trader_heatmap: 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.
trader_heatmap 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 trader_heatmap 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 trader_heatmap. 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.
trader_heatmap is provided by the Tradingview MCP server (lionfaion/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 →