Search for notes containing specific text in their content
AI agents call search_content to retrieve information from Obsidian Tools 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 information from the Obsidian vault by searching for text matches. It performs a read-only operation that returns results without altering any data. While the server offers destructive operations (delete_note) and write operations (create_note, append_to_note), this specific tool is purely informational.
From the tool's definition Tool name 'search_content' and description 'Search for notes containing specific text in their content' indicate a query/search operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Search for notes containing specific text in their content. It is categorised as a Read tool in the Obsidian Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Tools MCP Server MCP server in PolicyLayer and add a rule for search_content: 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 Tools MCP Server. Nothing to install.
search_content 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_content 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_content. 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_content is provided by the Obsidian Tools MCP Server MCP server (sureshsankaran/obsidian-tools-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 →