Search tokens by keyword using v2 API (broader results including DEX tokens).
AI agents call search_tokens_v2 to retrieve information from Bitget Wallet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves token information based on search criteria. It has no side effects on data or financial state—it only returns search results. Even though it searches across DEX tokens which operate on blockchains, the tool itself performs a read-only query operation with no ability to execute transactions, move funds, or modify state.
From the tool's definition Tool name 'search_tokens_v2' and description 'Search tokens by keyword' indicate a query operation. The broader server context mentions 'querying multi-chain token data' and 'retrieve real-time prices' as read-only operations.
Documented attack patterns abuse exactly the kind of access search_tokens_v2 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitget Wallet MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_tokens_v2:
{
"version": "1",
"default": "deny",
"tools": {
"search_tokens_v2": {}
}
}search_tokens_v2 is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search tokens by keyword using v2 API (broader results including DEX tokens). It is categorised as a Read tool in the Bitget Wallet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitget Wallet MCP Server MCP server in PolicyLayer and add a rule for search_tokens_v2: 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 Bitget Wallet MCP Server. Nothing to install.
search_tokens_v2 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 search_tokens_v2 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 search_tokens_v2. 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.
search_tokens_v2 is provided by the Bitget Wallet MCP Server MCP server (bitget-wallet-ai-lab/bitget-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitget Wallet MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Bitget Wallet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.