Wrap an unwrapped .eth name into the ENS NameWrapper contract. Wrapping converts the name from an ERC-721 token (BaseRegistrar) to an ERC-1155 token (NameWrapper). This enables: - Fuse permissions (restrict what can be done with the name) - Protected subnames (subnames with guaranteed permissions...
Part of the Name Whisper server.
Free to start. No card required.
AI agents may call wrap_name to permanently remove or destroy resources in Name Whisper. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call wrap_name in a loop, permanently destroying resources in Name Whisper. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"wrap_name"
]
}See the full Name Whisper policy for all 34 tools.
These attack patterns abuse exactly the kind of access wrap_name gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Wrap an unwrapped .eth name into the ENS NameWrapper contract. Wrapping converts the name from an ERC-721 token (BaseRegistrar) to an ERC-1155 token (NameWrapper). This enables: - Fuse permissions (restrict what can be done with the name) - Protected subnames (subnames with guaranteed permissions) - ERC-1155 compatibility for marketplaces and protocols Returns a two-step transaction recipe: approve + wrap. Available fuses (all IRREVERSIBLE once burned): - CANNOT_UNWRAP — prevents unwrapping back to BaseRegistrar - CANNOT_BURN_FUSES — prevents burning additional fuses - CANNOT_TRANSFER — prevents transfers - CANNOT_SET_RESOLVER — prevents resolver changes - CANNOT_SET_TTL — prevents TTL changes - CANNOT_CREATE_SUBDOMAIN — prevents new subnames - CANNOT_APPROVE — prevents approving operators CANNOT_UNWRAP must be burned before any other fuses can be burned.. It is categorised as a Destructive tool in the Name Whisper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Name Whisper MCP server in PolicyLayer and add a rule for wrap_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. Nothing to install.
wrap_name is a Destructive 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 wrap_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.
Set action: deny in the PolicyLayer policy for wrap_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.
wrap_name 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.