Change the resolver contract for an ENS name. The resolver is where a name's records live (ETH address, text records, content hash, etc.). Changing the resolver points the name at a different contract. Common use cases: - Migrating to the latest ENS Public Resolver - Pointing to a custom resolver...
Part of the Name Whisper — ENS Intelligence Layer server.
Free to start. No card required.
AI agents use set_resolver 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 set_resolver 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": {
"set_resolver": {
"limits": [
{
"counter": "set_resolver_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 set_resolver 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.
Change the resolver contract for an ENS name. The resolver is where a name's records live (ETH address, text records, content hash, etc.). Changing the resolver points the name at a different contract. Common use cases: - Migrating to the latest ENS Public Resolver - Pointing to a custom resolver (e.g. for off-chain/CCIP-read resolution) - Fixing a name that has no resolver set Pass "public" as the resolver address to use the ENS Public Resolver (0xF29100983E058B709F3D539b0c765937B804AC15). WARNING: Records on the old resolver won't be visible after switching. Set up records on the new resolver first, or use the ENS Public Resolver which most names already use.. 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 set_resolver: 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.
set_resolver 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 set_resolver 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 set_resolver. 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.
set_resolver 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.