search_memory

Federated keyword search across NodeBench

SERVERNodebench SOURCEnodebench-mcp

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/io-github-homenshum-nodebench/search-memory.md

WHAT IT DOES

What search_memory does on Nodebench

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

RISK

Why search_memory is rated Low

This tool performs a keyword search query across a system, which is a read-only operation. It retrieves or queries data without side effects, making it a Read category tool. The severity is low because search operations have minimal blast radius—the worst outcome would be retrieving unwanted information rather than causing system damage or data loss.

From the tool's definition Tool name 'search_memory' and description 'Federated keyword search across NodeBench' indicate a search operation that retrieves data without modifying it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_memory safely

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

search_memory Allowed

search_memory 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": {
    "search_memory": {}
  }
}

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

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

FAQ

Questions about search_memory

What does the search_memory tool do? +

Federated keyword search across NodeBench. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_memory? +

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

What risk level is search_memory? +

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

Can I rate-limit search_memory? +

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

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

search_memory is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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