memory_search_nodes

THE RISK

Low Risk

Why memory_search_nodes needs a policy

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.

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

POLICY

How to control memory_search_nodes

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

policy.json

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

memory_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 VaultAssist — 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 VaultAssist tools

Destructive batch_delete_gmail_emails Delete multiple emails at once Destructive clear_completed_tasks Clear all completed tasks from a task list. The tasks will be marked as hidden Destructive delete_event Delete an event from a Google Calendar Destructive delete_gmail_email Delete an email by its message ID Destructive delete_gmail_label Delete a Gmail label Destructive delete_task Delete a task from a task list Destructive delete_task_list Delete a task list. Note: This will also delete all tasks in the list Destructive memory_delete_entities Delete and forget multiple entities and their associated relationships from the user

All 79 VaultAssist 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 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.

Enforce policy on every VaultAssist tool call.

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

CHECK YOUR STACK →