Get tags from the vault, either all tags or for a specific file
AI agents call get_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 retrieves metadata (tags) from an Obsidian vault without modifying, creating, or deleting any data. It presents minimal security risk as it only queries and returns existing information. The low severity reflects that tag information in a personal knowledge base is unlikely to cause harm if exposed or accessed by an AI agent.
From the tool's definition Tool description states 'Get tags from the vault' - a retrieval operation with no modification or side effects. The verb 'Get' and the absence of any language indicating modification (create, update, delete, execute) confirms this is a read-only operation.
Documented attack patterns abuse exactly the kind of access get_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 get_tags:
{
"version": "1",
"default": "deny",
"tools": {
"get_tags": {}
}
}get_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.
Get tags from the vault, either all tags or for a specific file. 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 get_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.
get_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 get_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 get_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.
get_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.