check_sanctions_batch
chainpeek: Screen up to 1,000 crypto addresses against OFAC sanctions in one batch. For one address use check_sanctions. Returns the OFAC sanctions screen of 1-1,000 crypto addresses in one call. EVM and bech32 addresses match case-insensitively, other formats exactly as listed. US OFAC SDN digit...
This record as markdown: /tools/dev-tanod-tanod/check-sanctions-batch.md
What check_sanctions_batch does on Tanod
AI agents call check_sanctions_batch 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 |
|---|---|---|---|
addresses | array | Yes | 1-1,000 crypto addresses: EVM 0x (case-insensitive), bech32 (case-insensitive) or BTC/TRX/other exactly as listed. Priced per address. |
Parameters from the server's own tool schema.
Why check_sanctions_batch is rated Low
Even though check_sanctions_batch 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_sanctions_batch 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_sanctions_batch, this is the rule to start with:
check_sanctions_batch 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_sanctions_batch call is checked against it from then on.
Questions about check_sanctions_batch
chainpeek: Screen up to 1,000 crypto addresses against OFAC sanctions in one batch. For one address use check_sanctions. Returns the OFAC sanctions screen of 1-1,000 crypto addresses in one call. EVM and bech32 addresses match case-insensitively, other formats exactly as listed. US OFAC SDN digital-currency-address list only, as of list_date; a non-match does not clear an address; not legal advice or a full compliance check; verify any match at sanctionssearch.ofac.treas.gov. One invalid item fails the batch with a 422 naming its index (not charged). Typically under 0.5 s for 1,000 addresses. Price: USD 0.0005 per address, at least USD 0.002 per call (1-1,000 addresses per call: USD 0.002-0.5). No free tier. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/batch-ofac-sanctions-screening-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_sanctions_batch accepts 1 parameter: addresses. Required: addresses. 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_sanctions_batch: 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_sanctions_batch 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_sanctions_batch 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_sanctions_batch. 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_sanctions_batch 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