Search the vault for text, returns matching files with context
AI agents call search to retrieve information from Obsidian Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches the vault and returns matching files with context. It performs information retrieval only—no data is created, modified, deleted, or executed. This is a typical read operation with minimal risk if misused by an AI agent, as the worst outcome would be exposure of vault contents the agent is already authorized to access.
From the tool's definition Tool name 'search' and description 'Search the vault for text, returns matching files with context' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Search the vault for text, returns matching files with context. It is categorised as a Read tool in the Obsidian Local MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Local 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 Local. 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 Local MCP server (matthewsuazo/obsidian-local-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 →