Medium Risk

set_ens_records

Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), ENSIP-25 agent-registration records,...

Risk signalsHigh parameter count (16 properties)

Part of the Name Whisper — ENS Intelligence Layer server.

set_ens_records can modify Name Whisper — ENS Intelligence Layer data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Free to start. No card required.

AI agents use set_ens_records 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_ens_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 — ENS Intelligence Layer.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_ens_records": {
      "limits": [
        {
          "counter": "set_ens_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Name Whisper — ENS Intelligence Layer policy for all 42 tools.

Get this rule live on your own Name Whisper — ENS Intelligence Layer server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NAME WHISPER — ENS INTELLIGENCE LAYER →

View all 42 tools →

These attack patterns abuse exactly the kind of access set_ens_records gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so set_ens_records only ever does what you allow.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the set_ens_records tool do? +

Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), ENSIP-25 agent-registration records, and ENSIP-26 agent context and endpoint discovery. Multiple records are batched into a single multicall transaction to save gas. Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category. ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry. ENSIP-26 support: Pass agentContext to set the agent-context text record (free-form agent description). Pass agentEndpoints with protocol URLs (mcp, a2a, oasf, web) to set agent-endpoint[protocol] discovery records. The returned transaction can be signed and submitted directly using any wallet framework (Coinbase AgentKit, ethers.js, etc.).. 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.

How do I enforce a policy on set_ens_records? +

Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for set_ens_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 — ENS Intelligence Layer. Nothing to install.

What risk level is set_ens_records? +

set_ens_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_ens_records? +

Yes. Add a rate_limit block to the set_ens_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.

How do I block set_ens_records completely? +

Set action: deny in the PolicyLayer policy for set_ens_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.

What MCP server provides set_ens_records? +

set_ens_records 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.

Enforce policy on every Name Whisper — ENS Intelligence Layer tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.