search_nodes
Search for nodes in the knowledge graph based on query string, with optional tag and importance filtering
This record as markdown: /tools/danielsimonjr-memory-mcp/search-nodes.md
What search_nodes does on Enhanced Knowledge Graph Memory Server
AI agents call search_nodes to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_nodes is rated Low
This tool queries and retrieves data from a knowledge graph without creating, modifying, deleting, or executing external operations. The filtering parameters (query string, tags, importance) are all read-only filters. No data is altered, no code is executed, and no external systems are triggered. This is a standard data retrieval operation with minimal risk.
From the tool's definition Tool name is 'search_nodes' and description states it 'Search[es] for nodes in the knowledge graph based on query string, with optional tag and importance filtering' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_nodes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_nodes, this is the rule to start with:
search_nodes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every search_nodes call is checked against it from then on.
Questions about search_nodes
Search for nodes in the knowledge graph based on query string, with optional tag and importance filtering. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced 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 Enhanced 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 Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue