Unified search tool for finding knowledge nodes. Supports three modes:
AI agents call kg_search to retrieve information from Personal Kg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from a knowledge graph without producing side effects. It supports searching across knowledge nodes but does not create, modify, delete, or execute operations. The server's purpose is to capture and preserve decision context, and this tool serves the read/retrieval function within that system. No destructive, financial, or code execution capabilities are indicated.
From the tool's definition Tool name 'kg_search' and description explicitly states it is a 'search tool for finding knowledge nodes' with no mention of modification, deletion, execution, or financial operations. The verb 'finding' and 'search' indicate retrieval/query operations only.
Documented attack patterns abuse exactly the kind of access kg_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Personal Kg, and nothing reaches the server without passing your rules. This is the rule we recommend for kg_search:
{
"version": "1",
"default": "deny",
"tools": {
"kg_search": {}
}
} kg_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Unified search tool for finding knowledge nodes. Supports three modes:. It is categorised as a Read tool in the Personal Kg MCP Server, which means it retrieves data without modifying state.
Register the Personal Kg MCP server in PolicyLayer and add a rule for kg_search: 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 Personal Kg. Nothing to install.
kg_search 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 kg_search 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 kg_search. 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.
kg_search is provided by the Personal Kg MCP server (tomschell/personal-kg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Personal Kg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Personal Kg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.