AI agents call analyze_tags to retrieve information from Obsidian Ai Curator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs statistical or analytical examination of tags already present in the vault. Analysis is a read-only operation with no side effects, no data modification, no execution of external processes, and no destructive capability. The low severity reflects minimal risk even if misused—an AI agent could at worst generate reports on tag distribution, which poses no harm to data integrity or system security.
From the tool's definition Tool name 'analyze_tags' combined with description 'Analyze tag usage across the vault' indicates a query/analysis operation that retrieves and examines existing tag data without modifying or deleting anything.
Documented attack patterns abuse exactly the kind of access analyze_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_tags:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_tags": {}
}
}analyze_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.
Analyze tag usage across the vault. It is categorised as a Read tool in the Obsidian Ai Curator MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for analyze_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 Obsidian Ai Curator. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_tags is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, 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.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.