Real-time whale transfer alerts on Base and Ethereum. Returns list of large on-chain transfers with sender, receiver, token, amount, and USD value. Pass min_usd to set threshold (default $1M). Use to detect smart money movements or monitor an ecosystem for unusual capital flows.
AI agents call whale_alert to retrieve information from Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
min_usd | number | — |
Parameters from the server's own tool schema.
This tool retrieves and displays existing blockchain transfer data in real-time. It performs no writes, executions, or financial transactions — it purely queries and returns on-chain transfer information. No side effects are described. Severity is low because misuse only risks information disclosure, not direct harm.
From the tool's definition Returns list of large on-chain transfers with sender, receiver, token, amount, and USD value... Use to detect smart money movements or monitor an ecosystem for unusual capital flows.
Attacks that exploit this kind of access
Real-time whale transfer alerts on Base and Ethereum. Returns list of large on-chain transfers with sender, receiver, token, amount, and USD value. Pass min_usd to set threshold (default $1M). Use to detect smart money movements or monitor an ecosystem for unusual capital flows. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
whale_alert accepts 1 parameter: min_usd. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for whale_alert: 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 Mcp Server. Nothing to install.
whale_alert 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 whale_alert 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 whale_alert. 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.
whale_alert is provided by the Mcp Server MCP server (Homie4570/lso-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 →