Streaming search that yields results incrementally. Useful for large vaults where you want to see results as they are found. Streaming is used internally; the MCP tool returns a single response with all results (or up to limit).
AI agents call search_vault_stream 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 tool retrieves and queries data from an Obsidian vault without modifying, deleting, or executing anything. It is a pure read operation that searches for notes and returns matching results. There are no side effects or irreversible actions possible. Streaming is an implementation detail for efficiency but does not change the fundamental read-only nature of the operation.
From the tool's definition Tool is described as 'Streaming search that yields results incrementally' and 'returns a single response with all results'. The function name contains 'search' and 'vault', indicating data retrieval only.
Attacks that exploit this kind of access
Streaming search that yields results incrementally. Useful for large vaults where you want to see results as they are found. Streaming is used internally; the MCP tool returns a single response with all results (or up to limit). 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_stream: 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_stream 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_stream 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_stream. 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_stream 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 →