Search for nodes in the knowledge graph
AI agents call mcp_memory_search_nodes to retrieve information from MCP Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation on existing knowledge graph nodes, which is fundamentally a read operation. It retrieves or queries data with no capacity to create, modify, delete, or execute external operations. The search capability carries minimal risk - an AI agent misusing it could only over-query or extract information, but cannot alter the knowledge graph or trigger harmful side effects.
From the tool's definition Tool name 'search_nodes' and description 'Search for nodes in the knowledge graph' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Search for nodes in the knowledge graph. It is categorised as a Read tool in the MCP Memory Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for mcp_memory_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 MCP Memory Server. Nothing to install.
mcp_memory_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 mcp_memory_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 mcp_memory_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.
mcp_memory_search_nodes is provided by the MCP Memory Server MCP server (jessefreitas/mcp_memory). 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 →