Register multiple ENS names in bulk — batched into just 2 transactions (commit + register) via Multicall3. Much cheaper and faster than registering names one at a time. Supports up to 20 names per batch. Flow: batchCommit (1 tx) → wait 60 seconds → batchRegister (1 tx with total ETH). Excess ET...
Bulk/mass operation — affects multiple targets
Part of the Name Whisper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use bulk_register to create or modify resources in Name Whisper. 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 bulk_register repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Name Whisper.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
bulk_register:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Name Whisper policy for all 34 tools.
Agents calling write-class tools like bulk_register have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Register multiple ENS names in bulk — batched into just 2 transactions (commit + register) via Multicall3. Much cheaper and faster than registering names one at a time. Supports up to 20 names per batch. Flow: batchCommit (1 tx) → wait 60 seconds → batchRegister (1 tx with total ETH). Excess ETH is refunded. Each name gets its own secret for front-running protection. All names must be available for registration. After registration, use bulk_set_records to configure all names at once with addresses, text records, and content hashes.. It is categorised as a Write tool in the Name Whisper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for bulk_register. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Name Whisper MCP server.
bulk_register 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 bulk_register 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_register. 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_register 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