Low Risk

search_ens_names

Search ENS names using natural language. Supports all query types: - Filtered search: "4-letter words under 0.1 ETH" - Concept search: "ocean themed names" (semantic similarity across 3.6M names) - Creative search: "names for a coffee brand" (AI-generated suggestions) - Collection search: "crypto...

Accepts freeform code/query input (query)

Part of the Name Whisper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

namewhisper/ens-tools Read Risk 2/5

AI agents call search_ens_names to retrieve information from Name Whisper without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_ens_names only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

namewhisper-ens-tools.yaml
tools:
  search_ens_names:
    rules:
      - action: allow

See the full Name Whisper policy for all 34 tools.

Tool Name search_ens_names
Category Read
Risk Level Low

View all 34 tools →

Agents calling read-class tools like search_ens_names have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the search_ens_names tool do? +

Search ENS names using natural language. Supports all query types: - Filtered search: "4-letter words under 0.1 ETH" - Concept search: "ocean themed names" (semantic similarity across 3.6M names) - Creative search: "names for a coffee brand" (AI-generated suggestions) - Collection search: "crypto terms expiring soon" - Activity: "what sold recently?" - Availability check: "is coffee.eth taken?" - Bulk check: "check apple.eth, banana.eth, cherry.eth" Returns structured results with name, price, owner, tags, and availability info.. It is categorised as a Read tool in the Name Whisper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_ens_names? +

Add a rule in your Intercept YAML policy under the tools section for search_ens_names. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Name Whisper MCP server.

What risk level is search_ens_names? +

search_ens_names is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_ens_names? +

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

How do I block search_ens_names completely? +

Set action: deny in the Intercept policy for search_ens_names. 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 search_ens_names? +

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

Enforce policies on Name Whisper

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.