Low Risk

search_nodes

search_nodes

How to control search_nodes ↓

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

Low Risk

search_nodes performs a retrieval operation on graph data stored in Neo4j. It queries and returns node information without side effects. The naming convention aligns with read operations (search, get), and no write, delete, or execution indicators are present. Even with empty description, the name and context provide sufficient confidence that this is a read operation.

From the tool's definition Tool name 'search_nodes' indicates a query operation that retrieves nodes from a graph database. The description is empty, but the name and server context (Neo4j knowledge graph) clearly suggest this retrieves or searches data without modifying it.

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 Graphiti MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_nodes:

policy.json
{
  "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.

  1. Create a free account and register Graphiti MCP Server — 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.

Go deeper

What does the search_nodes tool do? +

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

How do I enforce a policy on search_nodes? +

Register the Graphiti MCP 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 Graphiti MCP Server. Nothing to install.

What risk level is search_nodes? +

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

Can I rate-limit search_nodes? +

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.

How do I block search_nodes completely? +

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.

What MCP server provides search_nodes? +

search_nodes is provided by the Graphiti MCP Server MCP server (rawr-ai/mcp-graphiti). 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 Server tool call.

Deterministic rules across all 8 Graphiti MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 Graphiti MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.