check_wallet_drain
chainpeek: Check a wallet for a drain: find tokens pulled out without its signature. For live approvals with revoke transactions use audit_token_approvals. Returns a verdict (drained | review | clean) for wallet over the latest 2,000 blocks: each transfer out of USDC and USDT (or up to 5 tokens) ...
This record as markdown: /tools/dev-tanod-tanod/check-wallet-drain.md
What check_wallet_drain does on Tanod
AI agents call check_wallet_drain to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | Yes | base or ethereum (the chains with built-in USDC and USDT here). |
tokens | object | — | 1 to 5 tokens: USDC, USDT or contract addresses. Default: USDC and USDT. |
wallet | string | Yes | The wallet to check (0x + 40 hex). |
lookback_blocks | integer | — | Latest blocks read (1-2,000; default 2,000, about 67 minutes on Base and 6.7 hours on Ethereum). |
Parameters from the server's own tool schema.
Why check_wallet_drain is rated Low
Even though check_wallet_drain only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs check_wallet_drain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_wallet_drain, this is the rule to start with:
check_wallet_drain is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every check_wallet_drain call is checked against it from then on.
Questions about check_wallet_drain
chainpeek: Check a wallet for a drain: find tokens pulled out without its signature. For live approvals with revoke transactions use audit_token_approvals. Returns a verdict (drained | review | clean) for wallet over the latest 2,000 blocks: each transfer out of USDC and USDT (or up to 5 tokens) is sent, authorized (EIP-3009, as x402 uses), wallet_code, pulled (someone else's transaction) or unknown, with the puller and its live allowance, the nonce before and after, and evidence. Drained: a pull to an address the wallet did not pay itself, or pulls of half of a token's holding. Review: other pulls, a balance that fell with an unmoved nonce, smart-account or EIP-7702 wallets. Gasless orders look like pulls. Bad input is a 422, a failed read a 502 (neither charged). Typically 2-10 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/wallet-drain-check-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_wallet_drain accepts 4 parameters: chain, tokens, wallet, lookback_blocks. Required: chain, wallet. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for check_wallet_drain: 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 Tanod. Nothing to install.
check_wallet_drain 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 check_wallet_drain 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 check_wallet_drain. 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.
check_wallet_drain is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue