Search for nodes in the knowledge graph based on a query
AI agents call search_nodes to retrieve information from Obsidian Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though search_nodes only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 Obsidian Memory MCP, 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 nodes in the knowledge graph based on a query. It is categorised as a Read tool in the Obsidian Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Memory 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 Obsidian Memory MCP. 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 Obsidian Memory MCP server (yunaga224/obsidian-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Obsidian Memory MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Obsidian Memory MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.