get_whale_alerts

Get whale-sized RWA transfers (>$50K USD). Filter by chain, category, type (mint/burn/transfer), and time window. Free tier shows 1h delayed data.

Server RWA Pipe MCP Server rwapipe/mcp
Category Read
Risk class Low
Parameters 00 required

What get_whale_alerts does on RWA Pipe MCP Server

AI agents call get_whale_alerts to retrieve information from RWA Pipe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_whale_alerts needs a policy

This tool retrieves and filters existing RWA transfer events from blockchain history. It has no side effects—it cannot create, modify, delete, or execute operations. Even though the data concerns large ('whale-sized') transfers, the tool itself only reads and presents information. The 1-hour delay for free tier further confirms historical data access rather than real-time execution.

From the tool's definition Tool name 'get_whale_alerts' and description indicate retrieval of historical transfer data with filtering options. Terms like 'get,' 'shows,' and 'delayed data' confirm read-only data querying with no modification, deletion, or execution capabilities.

Questions about get_whale_alerts

What does the get_whale_alerts tool do? +

Get whale-sized RWA transfers (>$50K USD). Filter by chain, category, type (mint/burn/transfer), and time window. Free tier shows 1h delayed data. It is categorised as a Read tool in the RWA Pipe MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_whale_alerts? +

Register the RWA Pipe MCP Server MCP server in PolicyLayer and add a rule for get_whale_alerts: 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 RWA Pipe MCP Server. Nothing to install.

What risk level is get_whale_alerts? +

get_whale_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_whale_alerts? +

Yes. Add a rate_limit block to the get_whale_alerts 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.

How do I block get_whale_alerts completely? +

Set action: deny in the PolicyLayer policy for get_whale_alerts. 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.

What MCP server provides get_whale_alerts? +

get_whale_alerts is provided by the RWA Pipe MCP Server MCP server (rwapipe/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.