Bulk-create subnames under a parent ENS name in a single transaction. Designed for agent fleet deployment — create identities like agent001.company.eth, agent002.company.eth, etc. Each subname can have its own owner and records (addresses, text records). All N subnames bundle into ONE NameWrapper...
Part of the Name Whisper — ENS Intelligence Layer server.
Free to start. No card required.
AI agents use mint_subnames to create or modify resources in Name Whisper — ENS Intelligence Layer. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call mint_subnames repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Name Whisper — ENS Intelligence Layer.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"mint_subnames": {
"limits": [
{
"counter": "mint_subnames_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Name Whisper — ENS Intelligence Layer policy for all 42 tools.
These attack patterns abuse exactly the kind of access mint_subnames gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Bulk-create subnames under a parent ENS name in a single transaction. Designed for agent fleet deployment — create identities like agent001.company.eth, agent002.company.eth, etc. Each subname can have its own owner and records (addresses, text records). All N subnames bundle into ONE NameWrapper.multicall transaction (all-or-nothing). All record updates across all subnames bundle into ONE Resolver.multicall transaction. If the parent is unwrapped, the recipe prepends a one-time wrap setup (approve + wrapETH2LD) — after that, every subsequent batch on the same parent is a single signature. Returns a flat steps[] array — each step is one wallet signature, in order. Subnames are free to create; only gas costs apply.. It is categorised as a Write tool in the Name Whisper — ENS Intelligence Layer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for mint_subnames: 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.
mint_subnames is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mint_subnames 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 mint_subnames. 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.
mint_subnames 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.
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.