Search for notes in the vault by query text. Searches in note titles and content. Returns matching notes with snippets, dates, and relevance scores. Supports filtering by folder/tag and sorting.
AI agents call search_notes to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_notes performs a read-only query operation against the Obsidian vault. It retrieves and returns matching notes with metadata (snippets, dates, relevance scores) but does not create, modify, delete, or execute any operations. The filtering and sorting parameters are read-side operations that refine the query results without side effects.
From the tool's definition Tool description states 'Search for notes in the vault by query text' and 'Returns matching notes with snippets, dates, and relevance scores.' The verb 'search' and return-only behavior with no modification capabilities indicate a retrieval operation.
Attacks that exploit this kind of access
Search for notes in the vault by query text. Searches in note titles and content. Returns matching notes with snippets, dates, and relevance scores. Supports filtering by folder/tag and sorting. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for search_notes: 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 MCP Server. Nothing to install.
search_notes 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_notes 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_notes. 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_notes is provided by the Obsidian MCP Server MCP server (senseibas/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →