Find all notes tagged with a specific tag, including nested sub-tags (searching
AI agents call search_by_tag to retrieve information from Obsidian Mcp Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for and retrieves notes based on tag criteria. It queries existing data without creating, modifying, deleting, or executing any operations. The verb 'find' combined with the read-only nature of tag-based search clearly places this in the Read category. Severity is low as misuse would only expose information already in the vault, not cause damage or irreversible changes.
From the tool's definition Tool name 'search_by_tag' and description 'Find all notes tagged with a specific tag' indicate a retrieval/query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access search_by_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Mcp Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for search_by_tag:
{
"version": "1",
"default": "deny",
"tools": {
"search_by_tag": {}
}
} search_by_tag 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.
Find all notes tagged with a specific tag, including nested sub-tags (searching. It is categorised as a Read tool in the Obsidian Mcp Pro MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Mcp Pro MCP server in PolicyLayer and add a rule for search_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 Pro. Nothing to install.
search_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_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_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_by_tag is provided by the Obsidian Mcp Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Mcp Pro, 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.
41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.