Search the Agent-Hive knowledge graph. Returns matching nodes, related edges, and demand signals.
AI agents call search_knowledge to retrieve information from Agent-hive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information from a knowledge graph with no side effects. It does not create, modify, delete, or execute operations. The sibling tools (create_node, edit_node, delete_node, create_edge) are separate and handle write/destructive operations. search_knowledge is a straightforward Read operation with minimal blast radius if misused—worst case an agent wastes compute on excessive queries.
From the tool's definition Tool description states it "Search[es] the Agent-Hive knowledge graph. Returns matching nodes, related edges, and demand signals." The verbs are retrieval-only: search and return data without modification.
Attacks that exploit this kind of access
Search the Agent-Hive knowledge graph. Returns matching nodes, related edges, and demand signals. It is categorised as a Read tool in the Agent-hive MCP Server, which means it retrieves data without modifying state.
Register the Agent-hive MCP server in PolicyLayer and add a rule for search_knowledge: 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 Agent-hive. Nothing to install.
search_knowledge is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_knowledge 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.
Set action: deny in the PolicyLayer policy for search_knowledge. 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.
search_knowledge is provided by the Agent-hive MCP server (kelvinyuefanli/agent-hive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →