General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to:...
Risk signalsAccepts freeform code/query input (query)
Part of the Nansen-MCP server.
Free to start. No card required.
AI agents call general_search 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 general_search 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": {
"general_search": {}
}
}See the full Nansen-MCP policy for all 24 tools.
These attack patterns abuse exactly the kind of access general_search 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.
General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol) Args: query: The search term - token symbol, name, or address. DO NOT include chain name here! result_type: Type filter - "token", "entity", "eoa", or "any" max_results: Maximum number of results (default: 25, max: 25) chain: Optional chain filter to narrow down token results to specific blockchain. If not further specified, leave it as None. If a chain is specified, ALWAYS use this parameter instead of adding chain name to the query string. Valid values: "ethereum", "solana", "base", "bnb", "polygon", "arbitrum", "avalanche", "optimism", etc. How to choose result_type: - token: Use when searching for a token by name, symbol, or contract address. CRITICAL: Use the chain parameter to filter by blockchain, NOT the query string! ✅ CORRECT: query="AAVE", chain="base" ❌ WRONG: query="AAVE base", chain=None - entity: Use when you want entity info by name/label (exchanges, funds, etc.) - eoa: Use when you have an address and need its labels or you have an ENS/SNS domain and need the resolved address - any: Mixed results (tokens/entities). Also auto-resolves ENS/SNS domains and, if token/entity results are empty and the query looks like an address, falls back to EOA labels. Important: - This is the only tool that can resolve domains. If you start from a domain, pass the Resolved Address to other tools. - DOMAINS: Strings ending in .eth (ENS) or .sol (SNS) are DOMAIN NAMES, not tokens. Use result_type="eoa" or "any" to resolve them. Examples: "vitalik.eth", "abracadabra.sol", "y22.eth" are domains that resolve to addresses. - DO NOT ASSUME that token is a NFT, always verify the name by using this tool first. - DO NOT add keyword token or chain names to the query string, unless this is explicitly in the token name or symbol! - Focus on popular chains like ethereum, solana, base and bnb when no chain is specified and the same token is deployed on multiple chains. - If a chain is specified, use the chain parameter to filter tokens by blockchain instead of including chain in query. - DO NOT rely on this endpoint for LATEST prices as this is delayed. Use token_ohlcv for latest prices.. 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 general_search: 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.
general_search 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 general_search 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 general_search. 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.
general_search 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.