Monitor on-chain large wallet movements: significant BTC and ETH transfers, exchange inflows (bearish — selling pressure) and outflows (bullish — self-custody), and smart money wallet behaviour. Use this tool when: - A crypto trading agent wants to detect institutional buying or selling before it...
AI agents call get_whale_tracker 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.
This tool retrieves and queries publicly available on-chain blockchain data about wallet movements and transfers. It provides market intelligence through data analysis but does not execute trades, modify state, or commit financial obligations.
From the tool's definition Tool description states it 'Monitor[s] on-chain large wallet movements' and 'detect[s]' transfers and flows. The verb 'monitor' and 'detect' indicate passive observation of public blockchain data.
Attacks that exploit this kind of access
Monitor on-chain large wallet movements: significant BTC and ETH transfers, exchange inflows (bearish — selling pressure) and outflows (bullish — self-custody), and smart money wallet behaviour. Use this tool when: - A crypto trading agent wants to detect institutional buying or selling before it hits price - You need to know if large amounts of BTC/ETH are moving to exchanges (sell signal) or away (hold/buy signal) - An agent is tracking known whale wallets for directional intelligence - A DeFi agent wants to detect large capital flows into or out of protocols Returns per transaction: wallet_address, amount_token, amount_usd, direction (EXCHANGE_INFLOW/EXCHANGE_OUTFLOW/WALLET_TO_WALLET), exchange (if applicable), timestamp, signal (BULLISH/BEARISH/NEUTRAL). Example: getWhaleTracker({ 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_whale_tracker: 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_whale_tracker 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_whale_tracker 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_whale_tracker. 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_whale_tracker 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 →