Set ENS resolver records for multiple names in a single transaction — bulk record editing. All record updates across all names are batched into one resolver.multicall() call. Much cheaper than setting records one name at a time. Supports the same record types as set_ens_records: address records (...
Risk signalsHigh parameter count (11 properties)
Part of the Name Whisper server.
Free to start. No card required.
AI agents use bulk_set_records 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_set_records 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.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"bulk_set_records": {
"limits": [
{
"counter": "bulk_set_records_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Name Whisper policy for all 34 tools.
These attack patterns abuse exactly the kind of access bulk_set_records 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.
Set ENS resolver records for multiple names in a single transaction — bulk record editing. All record updates across all names are batched into one resolver.multicall() call. Much cheaper than setting records one name at a time. Supports the same record types as set_ens_records: address records (ETH, BTC, SOL, etc.), text records (avatar, description, social handles, AI agent metadata), content hash (IPFS/IPNS), and ENSIP-25 agent-registration records. You can set different records for each name (e.g., unique avatars) or the same records across all names (e.g., same ETH address). Max 50 names per batch. The wallet signing the transaction must be the owner/manager of all included names.. 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.
Register the Name Whisper MCP server in PolicyLayer and add a rule for bulk_set_records: 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_set_records 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_set_records 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_set_records. 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_set_records 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.