get_large_transfers

[Pro tier] Get recent large transfers (whale movements) for a specific RWA token. Shows transfers above $100k threshold. Free keys receive 401 with upgrade URL.

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

What get_large_transfers does on RWA Pipe MCP Server

AI agents call get_large_transfers 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_large_transfers needs a policy

This tool queries and retrieves blockchain transaction data (whale movements) without creating, modifying, deleting, or executing any operations. It is a passive data retrieval function analogous to searching or listing transactions. The Pro tier access gating and API key validation are authentication controls, not indicators of a more severe category.

From the tool's definition Tool name 'get_large_transfers' and description stating it 'Get[s] recent large transfers' and 'Shows transfers' — purely retrieves historical blockchain transfer data with no modification, deletion, or execution capability.

Questions about get_large_transfers

What does the get_large_transfers tool do? +

[Pro tier] Get recent large transfers (whale movements) for a specific RWA token. Shows transfers above $100k threshold. Free keys receive 401 with upgrade URL. 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_large_transfers? +

Register the RWA Pipe MCP Server MCP server in PolicyLayer and add a rule for get_large_transfers: 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_large_transfers? +

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

Can I rate-limit get_large_transfers? +

Yes. Add a rate_limit block to the get_large_transfers 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_large_transfers completely? +

Set action: deny in the PolicyLayer policy for get_large_transfers. 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_large_transfers? +

get_large_transfers 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.