# check_address_poisoning

chainpeek: Check a transfer recipient for address poisoning: lookalikes in the sender's history. For balance, gas and blacklist checks too use transfer_preflight; for OFAC use check_sanctions. Returns a risk (high | medium | low) for paying to: reads from's transfers of one token (default USDC) over the last 2,000 blocks and finds addresses with to's first 4 and last 4 hex characters; each reason carries its evidence (tx hash, block, amount, direction). High: to was never paid and imitates an address from paid or a contact, or appears only in zero-value or dust transfers. Medium: a lookalike exists but to was paid or is a contact. Older history, other tokens and other lookalikes are not seen. Bad input is a 422, a failed read a 502 (neither charged). Typically 0.5-4 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/address-poisoning-check-api.html

Agent View of the PolicyLayer registry record for `check_address_poisoning`. HTML page: https://policylayer.com/tools/dev-tanod-tanod/check-address-poisoning

## Facts

- Tool: `check_address_poisoning`
- Server: Tanod (`https://tanod.dev/mcp`) — https://policylayer.com/tools/dev-tanod-tanod.md
- Homepage: https://github.com/https://tanod.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 7 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `to` | string | yes | The recipient about to be paid (0x + 40 hex). Must differ from `from`. |
| `from` | string | yes | The sending wallet whose transfer history is read (0x + 40 hex). |
| `chain` | string | yes | ethereum, base or robinhood (Robinhood Chain, chain id 4663). |
| `token` | string | no | USDC (default), USDT, or a token contract address. Only this token's transfers are read. On robinhood pass a contract address. |
| `contacts` | object | no | Up to 100 addresses you trust (your address book); `to` is compared with them too, without any chain read. |
| `dust_threshold` | object | no | Incoming transfers below this many token units count as dust. Default 0.01 for USDC and USDT; off for other tokens unless set; 0 turns it off. |
| `lookback_blocks` | integer | no | How many of the latest blocks of history to read (0-2,000; default 2,000, about 67 minutes on Base and 6.7 hours on Ethereum). 0 reads nothing and checks `conta |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_address_poisoning",
    "arguments": {
      "to": "<to>",
      "from": "<from>",
      "chain": "<chain>"
    }
  }
}
```

## Why check_address_poisoning is rated Low

Even though check_address_poisoning 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.

Risk signals: Handles credentials or secrets (token)

## Use case

AI agents call check_address_poisoning 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tanod:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_address_poisoning": {}
  }
}
```

## Other tools on Tanod (307)

- `audit_token_approvals` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/audit-token-approvals.md
- `aurora_forecast` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/aurora-forecast.md
- `diff_text` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/diff-text.md
- `image_metadata` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/image-metadata.md
- `pdf_pipeline` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/pdf-pipeline.md
- `pdf_protect` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/pdf-protect.md
- `pdf_remove_pages` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/pdf-remove-pages.md
- `pdf_reorder_pages` — Destructive — https://policylayer.com/tools/dev-tanod-tanod/pdf-reorder-pages.md
- `build_ics_event` — Execute — https://policylayer.com/tools/dev-tanod-tanod/build-ics-event.md
- `build_pptx_deck` — Execute — https://policylayer.com/tools/dev-tanod-tanod/build-pptx-deck.md
- `build_xlsx_workbook` — Execute — https://policylayer.com/tools/dev-tanod-tanod/build-xlsx-workbook.md
- `bulk_agent_index` — Execute — https://policylayer.com/tools/dev-tanod-tanod/bulk-agent-index.md
- `cron_next_runs` — Execute — https://policylayer.com/tools/dev-tanod-tanod/cron-next-runs.md
- `decode_calldata` — Execute — https://policylayer.com/tools/dev-tanod-tanod/decode-calldata.md
- `expand_rrule` — Execute — https://policylayer.com/tools/dev-tanod-tanod/expand-rrule.md
- `html_to_pdf` — Execute — https://policylayer.com/tools/dev-tanod-tanod/html-to-pdf.md
- `image_crop` — Execute — https://policylayer.com/tools/dev-tanod-tanod/image-crop.md
- `parse_ics` — Execute — https://policylayer.com/tools/dev-tanod-tanod/parse-ics.md
- `parse_phone_number` — Execute — https://policylayer.com/tools/dev-tanod-tanod/parse-phone-number.md
- `parse_rss_feed` — Execute — https://policylayer.com/tools/dev-tanod-tanod/parse-rss-feed.md
- `parse_sitemap` — Execute — https://policylayer.com/tools/dev-tanod-tanod/parse-sitemap.md
- `parse_url` — Execute — https://policylayer.com/tools/dev-tanod-tanod/parse-url.md
- `parse_user_agent` — Execute — https://policylayer.com/tools/dev-tanod-tanod/parse-user-agent.md
- `render_mermaid` — Execute — https://policylayer.com/tools/dev-tanod-tanod/render-mermaid.md
- `satellite_passes` — Execute — https://policylayer.com/tools/dev-tanod-tanod/satellite-passes.md
- `sec_financials` — Execute — https://policylayer.com/tools/dev-tanod-tanod/sec-financials.md
- `transcribe_audio` — Execute — https://policylayer.com/tools/dev-tanod-tanod/transcribe-audio.md
- `x402_well_known_file` — Execute — https://policylayer.com/tools/dev-tanod-tanod/x402-well-known-file.md
- `compare_stablecoin_transfer_fees` — Financial — https://policylayer.com/tools/dev-tanod-tanod/compare-stablecoin-transfer-fees.md
- `transfer_preflight` — Financial — https://policylayer.com/tools/dev-tanod-tanod/transfer-preflight.md
- …and 277 more: https://policylayer.com/tools/dev-tanod-tanod.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-tanod-tanod · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-tanod-tanod