memory_search_nodes

Search and find nodes in the user

SERVERVaultAssist SOURCE3xcaffeine/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3xcaffeine-mcp-server/memory-search-nodes.md

WHAT IT DOES

What memory_search_nodes does on VaultAssist

AI agents call memory_search_nodes to retrieve information from VaultAssist without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why memory_search_nodes is rated Low

This tool retrieves or queries data from memory/nodes without modifying, deleting, or executing operations. The 'search' verb and 'find' action are characteristic of Read category tools. While the description is minimal, the naming convention strongly suggests a search/lookup operation. Low severity because read-only access to memory nodes has minimal blast radius compared to write or destructive operations.

From the tool's definition Tool name contains 'search' and description indicates it 'Search and find nodes in the user', which are passive retrieval operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_search_nodes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultAssist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_search_nodes, this is the rule to start with:

memory_search_nodes Allowed

memory_search_nodes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_search_nodes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultAssist, apply this rule, and every memory_search_nodes call is checked against it from then on.

FAQ

Questions about memory_search_nodes

What does the memory_search_nodes tool do? +

Search and find nodes in the user. It is categorised as a Read tool in the VaultAssist MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_search_nodes? +

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

What risk level is memory_search_nodes? +

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

Can I rate-limit memory_search_nodes? +

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

How do I block memory_search_nodes completely? +

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

What MCP server provides memory_search_nodes? +

memory_search_nodes is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultAssist, and thousands of servers like it.

This server

All 79 VaultAssist tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →