Search for notes with enhanced folder and path matching
AI agents call search_notes to retrieve information from ObsidianReaderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search_notes tool retrieves or queries data from an Obsidian vault without side effects. It does not create, modify, delete, or execute external operations. Misuse by an AI agent would result in unauthorized information access but no data loss, no execution, and no financial impact. This is a standard Read category tool with low severity and high confidence.
From the tool's definition Tool name is 'search_notes' and description states it 'Search[es] for notes' — a retrieval operation with no modification or deletion capability. The broader server supports CRUD operations, but this specific tool performs query/search functionality only.
Attacks that exploit this kind of access
Search for notes with enhanced folder and path matching. It is categorised as a Read tool in the ObsidianReaderMCP MCP Server, which means it retrieves data without modifying state.
Register the ObsidianReader 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 ObsidianReaderMCP. 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 ObsidianReader MCP server (qianjue-cn/obsidianreadermcp). 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 →