Search files in vault with fuzzy matching. Use this when you don\
AI agents call find_files 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 tool retrieves/queries file locations based on fuzzy search patterns without modifying, executing, or deleting any data. It is a safe read operation with minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states 'Search files in vault with fuzzy matching' - this is a query/search operation with no side effects. Verb 'search' and 'find' are read-only operations.
Documented attack patterns abuse exactly the kind of access find_files 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 find_files:
{
"version": "1",
"default": "deny",
"tools": {
"find_files": {}
}
} find_files 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 files in vault with fuzzy matching. Use this when you don\. 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 find_files: 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.
find_files 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 find_files 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 find_files. 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.
find_files 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.