Search for entities and their relations using text or vector similarity
AI agents call search_nodes to retrieve information from MCP Memory LibSQL without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs queries against stored entities and relations without creating, modifying, or destroying data. It is a read-only operation with no side effects beyond retrieving and returning information. Severity is low because search operations have minimal blast radius — misuse returns data but does not alter state or trigger external operations.
From the tool's definition Tool name is 'search_nodes' and description states 'Search for entities and their relations using text or vector similarity' — pure retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access search_nodes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Memory LibSQL, and nothing reaches the server without passing your rules. This is the rule we recommend for search_nodes:
{
"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.
Free to start. No card required.
Search for entities and their relations using text or vector similarity. It is categorised as a Read tool in the MCP Memory LibSQL MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory LibSQL 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 MCP Memory LibSQL. Nothing to install.
search_nodes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
search_nodes is provided by the MCP Memory LibSQL MCP server (joleyline/mcp-memory-libsql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Memory LibSQL, 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.
6 MCP Memory LibSQL tools catalogued and risk-classified — across an index of 43,000+ MCP servers.