search_nodes

THE RISK

Low Risk

Why search_nodes needs a policy

This tool performs a search operation that retrieves existing nodes from a knowledge graph without creating, modifying, or deleting data. It is a read-only operation similar to list, get, or fetch operations. The low severity reflects minimal blast radius—an AI agent querying nodes cannot cause harm to the system state.

From the tool's definition Tool name 'search_nodes' and description 'Search for nodes in a specific project' indicate a query/retrieval operation with no modification or side effects.

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

POLICY

How to control search_nodes

PolicyLayer is an MCP gateway — it sits between your AI agents and Xgmem, 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.

Create a free account and register Xgmem — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Xgmem tools

Destructive delete_entities Delete multiple entities and their associated relations from the project knowledge graph Destructive delete_observations Delete specific observations from entities in the project knowledge graph Destructive delete_relations Delete multiple relations from the project knowledge graph Write add_graph_observations Add new observations to existing entities in the project knowledge graph. Write copy_memory Copy memory entities and their relations from one project to another Write create_entities Create multiple new entities in the project knowledge graph Write create_relations Create multiple new relations between entities in the project knowledge graph Write save_project_observations Save observations for a project to a separate file in the format { projectId, observations

All 14 Xgmem tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_nodes

What does the search_nodes tool do? +

Search for nodes in a specific project. It is categorised as a Read tool in the Xgmem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_nodes? +

Register the Xgmem 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 Xgmem. 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 Xgmem MCP server (meetdhanani17/xgmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xgmem tool call.

Start from Xgmem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →