Scan trade tapes for liquidity health, bot patterns, and tradeability. Returns permissive scoring - flags issues but shows all results. Use to filter pump/breakout signals or evaluate new coins.
AI agents call scan_liquidity 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.
Despite the aggressive trading context of this MCP server, scan_liquidity performs passive analysis only: it queries market data (trade tapes) and returns informational scores about liquidity health and bot patterns. It does not execute orders, modify positions, delete data, or move money.
From the tool's definition Tool description states it 'scan[s]' and 'returns' analysis results with 'permissive scoring' and flags - all read-only operations that retrieve and report data without modifying state or executing trades.
Attacks that exploit this kind of access
Scan trade tapes for liquidity health, bot patterns, and tradeability. Returns permissive scoring - flags issues but shows all results. Use to filter pump/breakout signals or evaluate new coins. 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_liquidity: 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_liquidity 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_liquidity 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_liquidity. 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_liquidity 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 →