Compare Volume Profiles between Aster and Hyperliquid. Identifies divergent POCs, liquidity imbalances, and which exchange is leading. Critical for finding institutional flow differences and arbitrage signals.
AI agents call vpvr_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.
The tool reads and compares volume profile data across two exchanges to surface analytical signals (POC divergence, liquidity imbalances, institutional flow). It does not execute trades, modify data, or commit financial obligations.
From the tool's definition 'Compare Volume Profiles between Aster and Hyperliquid. Identifies divergent POCs, liquidity imbalances, and which exchange is leading.' — purely analytical/comparative, no order execution or data modification implied.
Attacks that exploit this kind of access
Compare Volume Profiles between Aster and Hyperliquid. Identifies divergent POCs, liquidity imbalances, and which exchange is leading. Critical for finding institutional flow differences and arbitrage signals. 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 vpvr_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.
vpvr_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 vpvr_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 vpvr_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.
vpvr_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 →