Instant crypto market health check: 9 macro indicators (Fear & Greed, BTC dominance, funding rates, MVRV Z-Score, hash rate, active addresses, US net liquidity, stablecoin supply, altcoin cap) each scored favorable/neutral/unfavorable with exact values, plus a global risk_on/mixed/risk_off verdic...
AI agents call navi_crypto_health 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.
Despite the server's broader context mentioning USDC payments, this specific tool is a pure data retrieval and analysis service. It reads market indicators and returns scored assessments. The per-request payment is a billing mechanism for access, not a financial operation performed by the tool itself.
From the tool's definition Tool retrieves and queries crypto market health indicators (Fear & Greed, BTC dominance, funding rates, MVRV Z-Score, hash rate, active addresses, etc.) with no side effects. Description explicitly states 'no LLM, sub-second' query behavior.
Attacks that exploit this kind of access
Instant crypto market health check: 9 macro indicators (Fear & Greed, BTC dominance, funding rates, MVRV Z-Score, hash rate, active addresses, US net liquidity, stablecoin supply, altcoin cap) each scored favorable/neutral/unfavorable with exact values, plus a global risk_on/mixed/risk_off verdict and a deterministic summary. No LLM, sub-second. Per-indicator deep dives available. (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.
Register the Navi X402 MCP server in PolicyLayer and add a rule for navi_crypto_health: 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_crypto_health 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_crypto_health 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_crypto_health. 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_crypto_health 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 →