Get token list by timestamp (paginated). Useful for discovering new tokens.
AI agents call historical_coins 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 performs a read-only query of historical token data. It has no side effects, does not modify blockchain state, does not execute transactions, and does not involve financial operations. The low severity reflects that discovering past tokens poses minimal risk even if an AI agent misuses the capability, as it only accesses already-public historical information.
From the tool's definition The tool retrieves a paginated token list filtered by timestamp, explicitly described as 'useful for discovering new tokens.' The verbs and intent are purely query-based—'get' and 'list'—with no modification, deletion, or execution of operations.
Documented attack patterns abuse exactly the kind of access historical_coins 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 historical_coins:
{
"version": "1",
"default": "deny",
"tools": {
"historical_coins": {}
}
}historical_coins 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.
Get token list by timestamp (paginated). Useful for discovering new 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 historical_coins: 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.
historical_coins 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 historical_coins 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 historical_coins. 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.
historical_coins 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.