Context-aware search that returns surrounding content, not just matching lines
AI agents call search_context 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 performs context-aware searching within an Obsidian vault, which is fundamentally a read operation. It retrieves and returns data (matching lines plus surrounding context) without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal — an AI could waste resources or leak sensitive vault content, but cannot damage or alter the vault itself.
From the tool's definition Tool name is 'search_context' and description states it 'returns surrounding content' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Context-aware search that returns surrounding content, not just matching lines. 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_context: 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_context 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_context 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_context. 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_context 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 →