AI agents call search_vault to retrieve information from Obsidian MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query across the vault, returning results without side effects. It falls squarely into the Read category as it retrieves information without creating, modifying, deleting, executing external operations, or involving financial transactions. The low severity reflects that search operations have minimal blast radius even if misused by an AI agent.
From the tool's definition The tool is described as 'Search for content in the Obsidian vault', which is a read-only retrieval operation that queries and returns matching content without modifying data.
Documented attack patterns abuse exactly the kind of access search_vault gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_vault:
{
"version": "1",
"default": "deny",
"tools": {
"search_vault": {}
}
}search_vault 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 content in the Obsidian vault. It is categorised as a Read tool in the Obsidian MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian 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. 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 (newtype-01/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Obsidian MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Obsidian MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.