Low Risk

search_memory_nodes

search_memory_nodes

How to control search_memory_nodes ↓

What search_memory_nodes does on Graphiti MCP Demo

AI agents call search_memory_nodes to retrieve information from Graphiti MCP Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_memory_nodes needs a policy

Search operations on graph data structures are inherently read operations with no side effects. The tool queries existing memory nodes without modifying, deleting, or executing arbitrary operations. Confidence is slightly reduced due to the missing description, but the name and sibling tool patterns provide strong contextual evidence.

From the tool's definition Tool name 'search_memory_nodes' indicates a query/search operation on graph nodes. The pattern aligns with sibling tools like 'search_memory_facts' and 'get_episodes' which are retrieval operations.

Documented attack patterns abuse exactly the kind of access search_memory_nodes gives an agent:

How to control search_memory_nodes

PolicyLayer is an MCP gateway — it sits between your AI agents and Graphiti MCP Demo, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memory_nodes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_memory_nodes": {}
  }
}

search_memory_nodes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Graphiti MCP Demo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_memory_nodes

What does the search_memory_nodes tool do? +

search_memory_nodes. It is categorised as a Read tool in the Graphiti MCP Demo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_memory_nodes? +

Register the Graphiti MCP Demo MCP server in PolicyLayer and add a rule for search_memory_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 Graphiti MCP Demo. Nothing to install.

What risk level is search_memory_nodes? +

search_memory_nodes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_memory_nodes? +

Yes. Add a rate_limit block to the search_memory_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.

How do I block search_memory_nodes completely? +

Set action: deny in the PolicyLayer policy for search_memory_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.

What MCP server provides search_memory_nodes? +

search_memory_nodes is provided by the Graphiti MCP Demo MCP server (kartikk-26/graphiti-mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Graphiti MCP Demo tool call.

Start from Graphiti MCP Demo, 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.

8 Graphiti MCP Demo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.