Fundamentals engine for the HYPE token (Hyperliquid): live price, funding and open interest, fees and buyback flywheel, P/S valuation percentile, perp market share, unlock absorption and RSI timing - scored into 3 axes (engine health, climate, momentum) with a synthesized buy/hold/lighten recomme...
AI agents call navi_hype_engine to retrieve information from Navi X402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval and analysis tool. It returns financial metrics, technical indicators, and valuation analysis for the HYPE token, but does not move funds, execute trades, delete data, or run arbitrary code. The payment mechanism (USDC charged per call) is infrastructure billing, not a financial action by the tool itself.
From the tool's definition navi_hype_engine provides live price, funding, open interest, fees, P/S valuation percentile, perp market share, unlock absorption, RSI timing, and synthesized scores/recommendations.
Attacks that exploit this kind of access
Fundamentals engine for the HYPE token (Hyperliquid): live price, funding and open interest, fees and buyback flywheel, P/S valuation percentile, perp market share, unlock absorption and RSI timing - scored into 3 axes (engine health, climate, momentum) with a synthesized buy/hold/lighten recommendation and buy-zone detection. Proprietary methodology, deterministic, no LLM. (Paid via x402: $0.01 USDC per call on Base, settled automatically.). It is categorised as a Read tool in the Navi X402 MCP Server, which means it retrieves data without modifying state.
Register the Navi X402 MCP server in PolicyLayer and add a rule for navi_hype_engine: 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 Navi X402. Nothing to install.
navi_hype_engine 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 navi_hype_engine 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 navi_hype_engine. 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.
navi_hype_engine is provided by the Navi X402 MCP server (navi-x402-mcp). 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 →