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 buil...
Part of the Name Whisper server.
Free to start. No card required.
AI agents use bulk_transfer_ens_names to initiate financial transactions through Name Whisper. Financial operations involve real money and are irreversible once processed. PolicyLayer 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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"bulk_transfer_ens_names": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}See the full Name Whisper policy for all 34 tools.
These attack patterns abuse exactly the kind of access bulk_transfer_ens_names gives an agent. Each links to the full case and the policy that stops it:
Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
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.
Register the Name Whisper MCP server in PolicyLayer and add a rule for bulk_transfer_ens_names: 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 Name Whisper. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 34 Name Whisper tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.