Approve or revoke an operator for ENS contract interactions. An approved operator can transfer ANY token owned by the approver on the specified contract. This is setApprovalForAll — it covers all tokens, not just one. Contracts: - base_registrar — ERC-721 tokens (unwrapped .eth names) - name_wrap...
Part of the Name Whisper — ENS Intelligence Layer server.
Free to start. No card required.
AI agents use approve_operator 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 approve_operator 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": {
"approve_operator": {
"limits": [
{
"counter": "approve_operator_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 approve_operator 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.
Approve or revoke an operator for ENS contract interactions. An approved operator can transfer ANY token owned by the approver on the specified contract. This is setApprovalForAll — it covers all tokens, not just one. Contracts: - base_registrar — ERC-721 tokens (unwrapped .eth names) - name_wrapper — ERC-1155 tokens (wrapped names and subnames) - ens_registry — ENS node ownership Common use cases: - Approve NameWrapper on BaseRegistrar before wrapping a name - Approve a marketplace contract for trading - Approve a management contract for batch operations - Revoke a previously approved operator Contract addresses: - BaseRegistrar: 0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85 - NameWrapper: 0xD4416b13d2b3a9aBae7AcD5D6C2BbDBE25686401 - ENS Registry: 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e WARNING: Only approve addresses you trust. An approved operator can move ALL your names on that contract.. 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 approve_operator: 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.
approve_operator 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 approve_operator 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 approve_operator. 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.
approve_operator 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.