Low Risk

enumerate_entities

Enumerate ENS-friendly labels for a finite real-world entity category and report which are available vs registered. USE THIS for any query like "find me NBA hall of famers", "available Pixar films", "F1 drivers I can register", "Beatles songs that are open". The tool generates verified, correctly...

Part of the Name Whisper — ENS Intelligence Layer server.

enumerate_entities is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Free to start. No card required.

AI agents call enumerate_entities to retrieve information from Name Whisper — ENS Intelligence Layer 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 enumerate_entities 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "enumerate_entities": {}
  }
}

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 enumerate_entities 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 enumerate_entities only ever does what you allow.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the enumerate_entities tool do? +

Enumerate ENS-friendly labels for a finite real-world entity category and report which are available vs registered. USE THIS for any query like "find me NBA hall of famers", "available Pixar films", "F1 drivers I can register", "Beatles songs that are open". The tool generates verified, correctly-spelled ENS labels — do NOT enumerate entity names from your own context and pass them to check_availability, because models routinely misspell long-tail names (scottiepippin instead of scottiepippen) or invent people who don't exist (e.g. "johncarlton" as an NBA HOFer). This tool exists precisely to avoid that. DO NOT use this for: - Vibes / themes ("luxury watch names", "edgy crypto names") — use search_ens_names with concept_search instead. - ENS-native categories ("10k club", "3-letter words") — use search_ens_names with collection_search. - Single-name lookups — use check_availability. Returns a list of entries grouped by status. Each entry has the proper name (e.g. "Scottie Pippen") alongside the ENS label (scottiepippen.eth), so you can show users the human-readable name in your reply.. It is categorised as a Read tool in the Name Whisper — ENS Intelligence Layer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on enumerate_entities? +

Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for enumerate_entities: 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 enumerate_entities? +

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

Can I rate-limit enumerate_entities? +

Yes. Add a rate_limit block to the enumerate_entities 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 enumerate_entities completely? +

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

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