Deep dive on one HYPE engine signal: definition, why it matters for the flywheel, buy/neutral/sell thresholds and the raw inputs behind the current status. Valid names include fees-30d, revenue-annualized, ps-ratio, funding, market-share, price-7d, open-interest, volume-24h, tvl-bridge, hip3-rwa,...
AI agents call navi_hype_signal 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Signal id, e.g. fees-30d | ps-ratio | funding | market-share | buybacks-af | staking | hip3-rwa | momentum-rsi |
Parameters from the server's own tool schema.
This is a data retrieval and analysis tool. It reads market indicators and financial metrics to provide intelligence signals. While the underlying service is paid (in USDC), the tool itself performs no write operations, destructive actions, code execution, or financial transactions—it only fetches and analyzes information. The payment mechanism is handled separately by the server infrastructure, not by this tool.
From the tool's definition Retrieves and provides analysis of HYPE engine signals including 'definition, why it matters... buy/neutral/sell thresholds and raw inputs behind current status'.
Attacks that exploit this kind of access
Deep dive on one HYPE engine signal: definition, why it matters for the flywheel, buy/neutral/sell thresholds and the raw inputs behind the current status. Valid names include fees-30d, revenue-annualized, ps-ratio, funding, market-share, price-7d, open-interest, volume-24h, tvl-bridge, hip3-rwa, buybacks-af, staking, auction-hip3, mcap-fdv, momentum-rsi. (Paid via x402: $0.005 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.
navi_hype_signal accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Navi X402 MCP server in PolicyLayer and add a rule for navi_hype_signal: 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_signal 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_signal 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_signal. 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_signal 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 →