Scan ALL Aster-tradeable pairs using Binance as the data oracle. Combines institutional-grade signals: top trader positioning, real OI history, taker buy/sell flow, funding rates, and Binance kline volume analysis. Returns ranked, tiered signals you can execute on Aster. This is the primary scann...
AI agents call scan_binance_signals to retrieve information from Asterdex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this tool operates in a financial trading context and the signals it returns could be acted upon to move money, the tool itself performs read-only operations: scanning pairs, analyzing positioning, OI history, flows, and volumes. It does not execute trades, transfer funds, or make financial commitments.
From the tool's definition Tool 'scans' data and 'returns ranked, tiered signals'—it retrieves and analyzes market data from Binance without modifying, executing orders, or consuming financial resources directly.
Attacks that exploit this kind of access
Scan ALL Aster-tradeable pairs using Binance as the data oracle. Combines institutional-grade signals: top trader positioning, real OI history, taker buy/sell flow, funding rates, and Binance kline volume analysis. Returns ranked, tiered signals you can execute on Aster. This is the primary scanner for finding high-conviction setups. It is categorised as a Read tool in the Asterdex MCP Server, which means it retrieves data without modifying state.
Register the Asterdex MCP server in PolicyLayer and add a rule for scan_binance_signals: 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 Asterdex. Nothing to install.
scan_binance_signals 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 scan_binance_signals 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 scan_binance_signals. 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.
scan_binance_signals is provided by the Asterdex MCP server (tyranosurasmax/asterdex-mcp-server). 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 →