Low Risk

open_nodes

Open specific nodes in the knowledge graph by their names

How to control open_nodes ↓

What open_nodes does on MCP Neo4j Knowledge Graph Memory Server

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

Low Risk

Why open_nodes needs a policy

This tool fetches/retrieves specific nodes from the knowledge graph by their names. It is a read-only lookup operation with no write, execute, or destructive behavior. Misuse potential is low as it only exposes stored graph data.

From the tool's definition "Open specific nodes in the knowledge graph by their names" — retrieves specific nodes by name, no modification or side effects implied

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

How to control open_nodes

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Neo4j Knowledge Graph Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for open_nodes:

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

open_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 MCP Neo4j Knowledge Graph Memory 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.

Related tools and policies

Go deeper

Questions about open_nodes

What does the open_nodes tool do? +

Open specific nodes in the knowledge graph by their names. It is categorised as a Read tool in the MCP Neo4j Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on open_nodes? +

Register the MCP Neo4j Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for open_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 Neo4j Knowledge Graph Memory Server. Nothing to install.

What risk level is open_nodes? +

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

Can I rate-limit open_nodes? +

Yes. Add a rate_limit block to the open_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 open_nodes completely? +

Set action: deny in the PolicyLayer policy for open_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 open_nodes? +

open_nodes is provided by the MCP Neo4j Knowledge Graph Memory Server MCP server (jovanhsu/mcp-neo4j-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Neo4j Knowledge Graph Memory Server tool call.

Start from MCP Neo4j Knowledge Graph Memory Server, 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 MCP Neo4j Knowledge Graph Memory Server 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.