Detect early accumulation/distribution BEFORE price moves using Binance as primary data source. Uses LEADING indicators: OI change (real historical data), funding rate velocity, cross-exchange funding divergence, smart money positioning (top traders L/S), and taker flow. Much more predictive than...
AI agents call scan_accumulation 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.
scan_accumulation performs market analysis and indicator calculation based on historical and real-time data sources (OI change, funding rates, taker flow, top trader positioning). This is fundamentally a data retrieval and analysis operation with no side effects on trading positions, accounts, or financial state.
From the tool's definition Tool description uses language of detection and analysis: 'Detect early accumulation/distribution', 'Uses LEADING indicators', 'funding rate velocity', 'smart money positioning' — all observational activities.
Attacks that exploit this kind of access
Detect early accumulation/distribution BEFORE price moves using Binance as primary data source. Uses LEADING indicators: OI change (real historical data), funding rate velocity, cross-exchange funding divergence, smart money positioning (top traders L/S), and taker flow. Much more predictive than lagging oscillators. 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_accumulation: 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_accumulation 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_accumulation 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_accumulation. 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_accumulation 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 →