AI agents call scan_for_pumps_hl 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 queries market data to detect price movement patterns (pump signals). While it may inform trading decisions, the tool itself only reads and analyzes data; it produces no side effects, does not execute orders, and does not modify account state. It is purely informational, making it a Read category tool with low severity since misuse would only provide incorrect trading advice rather than cause direct harm.
From the tool's definition Tool name 'scan_for_pumps_hl' and description state it 'scan[s]' for 'signals' on Hyperliquid perps—a data retrieval operation that identifies market patterns without modifying state, executing trades, or moving funds.
Attacks that exploit this kind of access
Scan Hyperliquid perps for early pump signals. Identical to scan_for_pumps but for Hyperliquid exchange. 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_hl: 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_hl 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_hl 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_hl. 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_hl 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 →