Fetch live blockchain metrics: Bitcoin mempool congestion and fees, Ethereum gas oracle (slow/standard/fast), DeFi total value locked (TVL) across 500+ protocols, and top yield opportunities ranked by APY. Use this tool when: - An agent is about to send a transaction and needs current gas/fee est...
AI agents call get_onchain_data to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_onchain_data is a pure data retrieval tool. It queries public blockchain state (mempool, gas prices, TVL figures) and returns informational metrics. While the server supports financial transactions via USDC on Base Mainnet (x402), this particular tool performs no financial operations—it only gathers market signals and on-chain indicators.
From the tool's definition Tool fetches and returns live blockchain metrics: Bitcoin mempool congestion and fees, Ethereum gas oracle (slow/standard/fast), DeFi total value locked (TVL) across 500+ protocols, and top yield opportunities ranked by APY.
Attacks that exploit this kind of access
Fetch live blockchain metrics: Bitcoin mempool congestion and fees, Ethereum gas oracle (slow/standard/fast), DeFi total value locked (TVL) across 500+ protocols, and top yield opportunities ranked by APY. Use this tool when: - An agent is about to send a transaction and needs current gas/fee estimates - A DeFi agent wants to find the highest-yielding liquidity pools - You need to assess network health or congestion before executing on-chain - A macro agent wants on-chain data as a leading indicator of market activity Returns: BTC (mempool_size, fee_sat_vb_fast, fee_sat_vb_slow, hashrate, block_time), ETH (gas_gwei_slow/standard/fast, base_fee), DeFi (total_TVL_usd, top_protocols, top_yield_opportunities). Example: getOnchainData({ chain:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_onchain_data: 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 Omni Service Node. Nothing to install.
get_onchain_data 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 get_onchain_data 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 get_onchain_data. 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.
get_onchain_data is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →