AI agents call scan_for_pumps_cross 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.
This tool retrieves and analyzes market data (pump signals) from multiple exchanges to identify patterns. While the output (pump signal identification) could inform trading decisions, the tool itself only reads/queries data—it does not execute trades, move funds, or create/modify positions.
From the tool's definition Tool scans exchanges for pump signals and compares results across BOTH Aster and Hyperliquid. The term 'scan' and 'compare results' indicates data retrieval and analysis only. No execution, modification, deletion, or financial commitment occurs.
Attacks that exploit this kind of access
Scan BOTH Aster and Hyperliquid for pump signals and compare results. Finds pairs flagged on both exchanges (highest conviction), Aster-only, and Hyperliquid-only. 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_for_pumps_cross: 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_for_pumps_cross 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_for_pumps_cross 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_for_pumps_cross. 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_for_pumps_cross 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 →