Get TOTAL amount of tokens bought/sold by address for a token on DEX (Decentralised Exchanges) ONLY. Use this tool to find out WHO is buying or selling a token (on DEX) AND then you can check if they are liquidating profits or accumulating more. Returns: Aggregated buyer/seller activity as markdo...
Part of the Nansen-MCP server.
Free to start. No card required.
AI agents call token_who_bought_sold 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_who_bought_sold 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_who_bought_sold": {}
}
}See the full Nansen-MCP policy for all 24 tools.
These attack patterns abuse exactly the kind of access token_who_bought_sold 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 TOTAL amount of tokens bought/sold by address for a token on DEX (Decentralised Exchanges) ONLY. Use this tool to find out WHO is buying or selling a token (on DEX) AND then you can check if they are liquidating profits or accumulating more. Returns: Aggregated buyer/seller activity as markdown. Returns empty string if no trading data found. Columns returned: - Address: Trader's wallet address - Label: Nansen label of the address - Bought Token Volume: Total quantity of tokens purchased - Sold Token Volume: Total quantity of tokens sold - Gross Token Volume: Combined buy and sell volume in tokens - Bought Volume USD: USD value of all token purchases - Sold Volume USD: USD value of all token sales - Gross Volume USD: Combined USD trading volume Sorting Options: You can sort asc or desc by bought_volume_usd or sold_volume_usd Notes: - buy_or_sell parameter filters for "BUY" (net buyers) or "SELL" (net sellers) - Aggregates all trading activity within the specified time range. 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_who_bought_sold: 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_who_bought_sold 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_who_bought_sold 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_who_bought_sold. 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_who_bought_sold 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.