Low Risk

kfdb_search_agents

Search 133K+ ERC-8004 agents indexed in KFDB by name, description, or chain. Uses semantic search when available, falls back to text matching. Returns agents with trust labels and rich metadata from the knowledge graph.

Accepts freeform code/query input (query); Single-target operation

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

@rickydata/agent0-mcp Read Risk 2/5

AI agents call kfdb_search_agents to retrieve information from Agent0 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 kfdb_search_agents 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.

agent0.yaml
tools:
  kfdb_search_agents:
    rules:
      - action: allow

See the full Agent0 policy for all 34 tools.

Tool Name kfdb_search_agents
Category Read
MCP Server Agent0 MCP Server
Risk Level Low

View all 34 tools →

Agents calling read-class tools like kfdb_search_agents 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 kfdb_search_agents tool do? +

Search 133K+ ERC-8004 agents indexed in KFDB by name, description, or chain. Uses semantic search when available, falls back to text matching. Returns agents with trust labels and rich metadata from the knowledge graph.. It is categorised as a Read tool in the Agent0 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kfdb_search_agents? +

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

What risk level is kfdb_search_agents? +

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

Can I rate-limit kfdb_search_agents? +

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

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

kfdb_search_agents is provided by the Agent0 MCP server (@rickydata/agent0-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Agent0

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.