Low Risk

search_agent_directory

Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OA...

Risk signalsAccepts freeform code/query input (query)

Part of the Name Whisper server.

search_agent_directory 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 →

Free to start. No card required.

AI agents call search_agent_directory 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_agent_directory 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": {
    "search_agent_directory": {}
  }
}

See the full Name Whisper policy for all 34 tools.

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

ENFORCE ON MY NAME WHISPER →

View all 34 tools →

These attack patterns abuse exactly the kind of access search_agent_directory 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 search_agent_directory only ever does what you allow.

SECURE NAME WHISPER →

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

What does the search_agent_directory tool do? +

Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents. 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_agent_directory? +

Register the Name Whisper MCP server in PolicyLayer and add a rule for search_agent_directory: 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. Nothing to install.

What risk level is search_agent_directory? +

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

Can I rate-limit search_agent_directory? +

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

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

search_agent_directory is provided by the Name Whisper MCP server (namewhisper/ens-tools). 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 tool call.

Deterministic rules across all 34 Name Whisper 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.