Critical Risk →

transfer_ens_name

Transfer ownership of an ENS name to another wallet address. Automatically detects whether the name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transaction. Requirements: - The fromAddress must currently own the name - The recipient (toAddress) ma...

Part of the Name Whisper — ENS Intelligence Layer server.

transfer_ens_name can move real money through Name Whisper — ENS Intelligence Layer, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Free to start. No card required.

AI agents use transfer_ens_name to initiate financial transactions through Name Whisper — ENS Intelligence Layer. 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.

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

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

See the full Name Whisper — ENS Intelligence Layer policy for all 42 tools.

Get this rule live on your own Name Whisper — ENS Intelligence Layer server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NAME WHISPER — ENS INTELLIGENCE LAYER →

View all 42 tools →

These attack patterns abuse exactly the kind of access transfer_ens_name gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so transfer_ens_name only ever does what you allow.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the transfer_ens_name tool do? +

Transfer ownership of an ENS name to another wallet address. Automatically detects whether the name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transaction. Requirements: - The fromAddress must currently own the name - The recipient (toAddress) may be a 0x address or an ENS name — names resolve to their address record - The name must be registered (not expired) WARNING: This transfers FULL ownership. The recipient gains complete control including the ability to transfer, set records, or let the name expire. Resolver records (avatar, addresses, etc.) are NOT affected by transfer — they stay on the name.. It is categorised as a Financial tool in the Name Whisper — ENS Intelligence Layer MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_ens_name? +

Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for transfer_ens_name: 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 — ENS Intelligence Layer. Nothing to install.

What risk level is transfer_ens_name? +

transfer_ens_name 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_ens_name? +

Yes. Add a rate_limit block to the transfer_ens_name 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_ens_name completely? +

Set action: deny in the PolicyLayer policy for transfer_ens_name. 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_ens_name? +

transfer_ens_name is provided by the Name Whisper — ENS Intelligence Layer MCP server (https://namewhisper.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Name Whisper — ENS Intelligence Layer tool call.

Deterministic rules across all 42 Name Whisper — ENS Intelligence Layer 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.