AI agents call token_info 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.
The tool name and position within a cohesive set of data-retrieval tools strongly suggests it queries token information without side effects. The server explicitly states it allows users to 'retrieve real-time prices' and 'query multi-chain token data'. No modification, execution, deletion, or financial action is indicated.
From the tool's definition Tool name 'token_info' and server context indicating it retrieves 'multi-chain token data' and 'real-time prices' alongside sibling tools like 'batch_token_info', 'coin_market_info', 'get_token_list', 'historical_coins', and 'holders_info' all of which are…
Documented attack patterns abuse exactly the kind of access token_info 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 token_info:
{
"version": "1",
"default": "deny",
"tools": {
"token_info": {}
}
}token_info 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.
token_info. 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 token_info: 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.
token_info 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_info 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_info. 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_info 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.