Full-text search across the vault with context lines
AI agents call vault_search to retrieve information from Mcp Obsidian Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on vault contents. It searches and returns matching text with surrounding context, with no capability to create, modify, delete, or execute operations. The blast radius is minimal — an AI agent using this tool can only discover information already present in the vault, creating no side effects on the system.
From the tool's definition Tool description states 'Full-text search across the vault with context lines' — a query operation that retrieves data without modifying or executing anything.
Attacks that exploit this kind of access
Full-text search across the vault with context lines. It is categorised as a Read tool in the Mcp Obsidian Planner MCP Server, which means it retrieves data without modifying state.
Register the Mcp Obsidian Planner MCP server in PolicyLayer and add a rule for vault_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 Mcp Obsidian Planner. Nothing to install.
vault_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 vault_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 vault_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.
vault_search is provided by the Mcp Obsidian Planner MCP server (jarero321/mcp-obsidian-planner). 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 →