Search for notes in Obsidian vault by content or title
AI agents call search_obsidian_notes to retrieve information from Obsidian Translation 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 existing notes without creating, modifying, deleting, or executing any operations. It is a straightforward search function that matches the Read category definition of querying data with no side effects.
From the tool's definition Tool description explicitly states 'Search for notes in Obsidian vault by content or title' — a pure query operation with no side effects. Server description confirms it 'search[es]' notes as a read-only function.
Attacks that exploit this kind of access
Search for notes in Obsidian vault by content or title. It is categorised as a Read tool in the Obsidian Translation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Translation MCP Server MCP server in PolicyLayer and add a rule for search_obsidian_notes: 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 Translation MCP Server. Nothing to install.
search_obsidian_notes 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_obsidian_notes 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_obsidian_notes. 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_obsidian_notes is provided by the Obsidian Translation MCP Server MCP server (nojiritakeshi/obsidian-translate-mcp-server). 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 →