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.

Risk signalsAccepts freeform code/query input (query)

Part of the Agent0 server.

kfdb_search_agents 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 AGENT0 →

Free to start. No card required.

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.

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

See the full Agent0 policy for all 34 tools.

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

ENFORCE ON MY AGENT0 →

View all 34 tools →

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

SECURE AGENT0 →

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

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? +

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

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 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 kfdb_search_agents completely? +

Set action: deny in the PolicyLayer 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent0 tool call.

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