Search for text inside file contents recursively across entire vault. Use this to find files containing specific text (like grep).
AI agents call search to retrieve information from Obsidian HTTP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search tool only reads and queries file contents to locate matches. It has no ability to modify, delete, or execute code. The grep analogy confirms it is a standard read-only search utility. Blast radius is minimal — misuse results only in unintended information disclosure of vault contents, not data loss or execution.
From the tool's definition Tool description states 'Search for text inside file contents recursively across entire vault' and 'like grep' — this is a search/query operation that retrieves matching files and content without modifying data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian HTTP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search 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 text inside file contents recursively across entire vault. Use this to find files containing specific text (like grep). It is categorised as a Read tool in the Obsidian HTTP MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian HTTP MCP server in PolicyLayer and add a rule for search: 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 HTTP MCP. Nothing to install.
search 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 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. 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 is provided by the Obsidian HTTP MCP server (nasandnora/obsidian-http-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian HTTP MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Obsidian HTTP MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.