Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. NOTE: This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - Time: Timestamp whe...
Part of the Nansen-MCP server.
Free to start. No card required.
AI agents call token_transfers to retrieve information from Nansen-MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though token_transfers only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"token_transfers": {}
}
}See the full Nansen-MCP policy for all 24 tools.
These attack patterns abuse exactly the kind of access token_transfers gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. NOTE: This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - Time: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format) - From Label: Source address label (from_address_label: sender of tokens) - To Label: Destination address label (to_address_label: receiver of tokens) - From Address: Raw source address (from_address: hex address) - To Address: Raw destination address (to_address: hex address) - Amount: Quantity of tokens transferred (transfer_amount: numeric) - Value USD: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted) - Type: Transfer category (transaction_type: DEX, CEX, transfer, etc.) - Tx Hash: Blockchain transaction hash for verification (transaction_hash) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount, valueUsd Examples: # Basic request (most recent transfers first) { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "order_by": "timestamp", "order_by_direction": "desc" } # Smart money only filter (largest transfers first) { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "transferOriginCategories": ["all_transfers"], "onlySmartTradersAndFunds": true, "order_by": "valueUsd", "order_by_direction": "desc" } # Filter by DEX only with minimum transfer value (USD) { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "transferOriginCategories": ["dex"], "transferValueUsd": {"from": 1000} } Available Filters: Transfer Origin Categories: - transferOriginCategories (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples: - ['dex'] - only DEX transfers - ['cex'] - only CEX transfers - ['dex', 'cex'] - both DEX and CEX - ['non_exchange_transfers'] - only non-exchange transfers - ['all_transfers'] - all types (default) Smart Money Filter: - onlySmartTradersAndFunds (bool): Only show smart money transfers (default: false) When true, filters to show only transfers involving profitable addresses Numeric Range Filter: - transferValueUsd (object, optional): Filter by USD value of transfer Format: {"from": X, "to": Y} or {"from": X} or {"to": Y} - Specify only from for minimum bound (no maximum) - Specify only to for maximum bound (no minimum) - Specify both for a bounded range Example: {"from": 1000} - only transfers worth at least $1,000 USD Example: {"to": 50000} - only transfers up to $50,000 USD Example: {"from": 1000, "to": 50000} - transfers between $1,000 and $50,000 USD Note: This filters by the USD value of the transfer at time of transaction Notes: - Use transferOriginCategories to control which transfer origins are included - Smart Money filter shows only transfers involving profitable addresses (definition of *Smart Money*) - transferValueUsd filters by USD value at time of transaction. It is categorised as a Read tool in the Nansen-MCP MCP Server, which means it retrieves data without modifying state.
Register the Nansen- MCP server in PolicyLayer and add a rule for token_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 Nansen-MCP. Nothing to install.
token_transfers 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 token_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.
Set action: deny in the PolicyLayer policy for token_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.
token_transfers is provided by the Nansen- MCP server (nansen-ai/Nansen-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Nansen-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.