search_notes_by_tag
AI agents call search_notes_by_tag 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.
Search operations query and retrieve data without modification or side effects. No deletion, creation, modification, execution, or financial operations occur. The empty description reduces confidence slightly, but the naming convention and context from sibling tools strongly indicate this is a read-only search function.
From the tool's definition Tool name 'search_notes_by_tag' indicates a search operation. Sibling tools like 'list_notes_in_folder' and 'list_obsidian_notes' establish this server's pattern of read-only queries. The server description emphasizes 'search' as a data retrieval capability.
Attacks that exploit this kind of access
search_notes_by_tag. 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_notes_by_tag: 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_notes_by_tag 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_notes_by_tag 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_notes_by_tag. 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_notes_by_tag is provided by the Obsidian MCP Server MCP server (nbaradar/obsidian-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 →