transfer_preflight

SERVERTanod SOURCEhttps://tanod.dev/mcp

Critical RISK CLASS

Category Financial

Parameters 55 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/transfer-preflight.md

WHAT IT DOES

What transfer_preflight does on Tanod

AI agents use transfer_preflight to commit financial operations through Tanod, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`to`	string	Yes	The recipient (0x + 40 hex).
`from`	string	Yes	The sending wallet (0x + 40 hex).
`chain`	string	Yes	ethereum, base, polygon, bnb or arbitrum.
`token`	string	Yes	USDC, USDT (the chain's native issuer contract) or an ERC-20 contract address.
`amount`	string	Yes	Amount in token units as a positive decimal string, e.g. "250.5" (not raw units).

Parameters from the server's own tool schema.

RISK

Why transfer_preflight is rated Critical

transfer_preflight moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Risk signalsHandles credentials or secrets (token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_preflight 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 transfer_preflight, this is the rule to start with:

transfer_preflight Approval-gated

Any call to transfer_preflight is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_preflight": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every transfer_preflight call is checked against it from then on.

FAQ

Questions about transfer_preflight

What does the transfer_preflight tool do? +

chainpeek: Preflight a USDC or USDT transfer: balance, gas, nonce, blacklist, recipient, simulation. For OFAC screening use check_sanctions; for a wallet's past pulls use check_wallet_drain. Returns a verdict (pass, warn or fail) for one planned ERC-20 transfer, with a row per check in checks (token balance, gas balance, pending nonce, issuer blacklist for sender and recipient, paused, recipient sanity, address-poisoning lookalike, simulated transfer(to, amount) with its revert reason, decimals and raw amount) and the non-passing ones in reasons. Read-only: nothing is signed or sent. A part that cannot be read is not_checked with a reason (verdict warn); a token without the blacklist function is not_available, not a fail. Lookalike check on Ethereum and Base only. Bad input is a 422 (not charged). Typically 1-4 s. Price: USD 0.01. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/gas-price-api.html. It is categorised as a Financial tool in the Tanod MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does transfer_preflight accept? +

transfer_preflight accepts 5 parameters: to, from, chain, token, amount. Required: to, from, chain, token, amount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on transfer_preflight? +

Register the Tanod MCP server in PolicyLayer and add a rule for transfer_preflight: 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.

What risk level is transfer_preflight? +

transfer_preflight is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_preflight? +

Yes. Add a rate_limit block to the transfer_preflight 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.

How do I block transfer_preflight completely? +

Set action: deny in the PolicyLayer policy for transfer_preflight. 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.

What MCP server provides transfer_preflight? +

transfer_preflight 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.

KEEP EXPLORING

More on Tanod, and thousands of servers like it.

This server

All 308 Tanod tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge →transfer_sites on A3plus → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →