AI agents call search_by_tags to retrieve information from Enhanced Obsidian 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 or queries data from the Obsidian vault based on tag filters. The action is a pure read operation with no side effects, reversible modifications, code execution, data destruction, or financial impact. The blast radius of misuse is minimal—an AI agent could retrieve unintended notes but cannot alter, delete, or execute operations.
From the tool's definition Tool name 'search_by_tags' and description 'Search notes by tags' indicate a query operation that retrieves notes matching tag criteria without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access search_by_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Enhanced Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_by_tags:
{
"version": "1",
"default": "deny",
"tools": {
"search_by_tags": {}
}
} search_by_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search notes by tags. It is categorised as a Read tool in the Enhanced Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Obsidian MCP Server MCP server in PolicyLayer and add a rule for search_by_tags: 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 Enhanced Obsidian MCP Server. Nothing to install.
search_by_tags 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_by_tags 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_by_tags. 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_by_tags is provided by the Enhanced Obsidian MCP Server MCP server (jianruidutong/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Enhanced Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Enhanced Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.