Transfer multiple ENS names in a single transaction via Multicall3 — bulk send. Much cheaper and faster than transferring names one at a time. Supports up to 20 names per batch. Automatically detects whether each name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and bu...
Part of the Name Whisper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use bulk_transfer_ens_names to initiate financial transactions through Name Whisper. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
bulk_transfer_ens_names moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
tools:
bulk_transfer_ens_names:
rules:
- action: deny
reason: "Requires human approval"See the full Name Whisper policy for all 34 tools.
Agents calling financial-class tools like bulk_transfer_ens_names have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Financial risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
bulk_transfer_ens_names is one of the critical-risk operations in Name Whisper. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Transfer multiple ENS names in a single transaction via Multicall3 — bulk send. Much cheaper and faster than transferring names one at a time. Supports up to 20 names per batch. Automatically detects whether each name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transfer call for each. All names can go to the same recipient or to different recipients — specify a toAddress per name. Requirements: - The fromAddress must currently own ALL names in the batch - All addresses must be valid Ethereum addresses - Names must be registered (not expired) WARNING: This transfers FULL ownership of every name. Recipients gain complete control. Resolver records (avatar, addresses, etc.) are NOT affected by transfer — they stay on each name. After transfer, consider using bulk_set_records to update ETH address records on the transferred names.. It is categorised as a Financial tool in the Name Whisper MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for bulk_transfer_ens_names. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Name Whisper MCP server.
bulk_transfer_ens_names is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bulk_transfer_ens_names rule in your Intercept 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 Intercept policy for bulk_transfer_ens_names. 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.
bulk_transfer_ens_names is provided by the Name Whisper MCP server (namewhisper/ens-tools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept