Search for nodes in the knowledge graph based on a query
AI agents call search_nodes to retrieve information from Knowledge Graph Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query/search operation against the knowledge graph, returning matching nodes without side effects. This is a classic Read operation—it retrieves data but does not create, modify, delete, or execute anything. The low severity reflects that querying a knowledge graph poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'search_nodes' and description 'Search for nodes in the knowledge graph based on a query' indicate a read-only retrieval operation. No modification, deletion, or execution of external operations is described.
Documented attack patterns abuse exactly the kind of access search_nodes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Knowledge Graph Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_nodes:
{
"version": "1",
"default": "deny",
"tools": {
"search_nodes": {}
}
}search_nodes 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.
Search for nodes in the knowledge graph based on a query. It is categorised as a Read tool in the Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for search_nodes: 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 Knowledge Graph Memory Server. Nothing to install.
search_nodes 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_nodes 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_nodes. 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_nodes is provided by the Knowledge Graph Memory Server MCP server (t1nker-1220/memories-with-lessons-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Knowledge Graph Memory Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Knowledge Graph Memory Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.