Search for content in the Obsidian vault (simplified interface). Requires a query parameter. Supports glob patterns, regex, pagination (limit/offset), score filtering (minScore), and tag/frontmatter filtering. Internally uses advanced_search_vault.
AI agents call search_vault 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.
This is a query/search tool that retrieves and filters existing vault content without modifying, deleting, or executing external operations. It has no side effects beyond returning search results. Severity is low because misuse would only expose existing notes the user already has access to within their vault—no data loss, financial impact, or code execution risk.
From the tool's definition Tool description explicitly states 'Search for content in the Obsidian vault' with support for 'query parameter', 'glob patterns', 'regex', 'pagination', 'score filtering', and 'tag/frontmatter filtering'.
Attacks that exploit this kind of access
Search for content in the Obsidian vault (simplified interface). Requires a query parameter. Supports glob patterns, regex, pagination (limit/offset), score filtering (minScore), and tag/frontmatter filtering. Internally uses advanced_search_vault. 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_vault: 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_vault 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_vault 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_vault. 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_vault is provided by the Obsidian MCP Server MCP server (markheramis/obsidian-mcp). 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 →