AI agents call search_tokens 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.
Despite the empty description, the tool name 'search_tokens' and the context of sibling tools strongly suggest this is a data retrieval function. The server's stated purpose is to expose APIs for querying token data, security audits, and market statistics. No indication of write, execute, destructive, or financial capabilities.
From the tool's definition Tool name 'search_tokens' with empty description; sibling tools on this server include 'batch_token_info', 'get_token_list', 'coin_market_info', 'kline', and 'balance', all of which are query/retrieval operations.
Documented attack patterns abuse exactly the kind of access search_tokens 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:
{
"version": "1",
"default": "deny",
"tools": {
"search_tokens": {}
}
}search_tokens 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. 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: 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 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 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. 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 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.