Enumerate every unique tag used across the vault along with the number of notes each tag appears in. Detects tags from both inline #hashtags and YAML frontmatter, normalizes them case-insensitively, and returns a sorted list plus the total unique tag count. Use to build a tag cloud, pick categori...
AI agents call list_tags 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.
list_tags retrieves and queries vault tag data without creating, modifying, or deleting any content. It is a read-only enumeration operation that serves discovery and auditing purposes. The context of sibling tools like delete_note and edit_block reinforces that this tool performs no mutations. Severity is low because reading tag metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool enumerates and returns tag metadata across the vault with no modification capability. The description explicitly states it returns 'a sorted list' and is used to 'discover available tags' and 'build a tag cloud'—purely informational operations with no…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list_tags 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 list_tags:
{
"version": "1",
"default": "deny",
"tools": {
"list_tags": {}
}
}list_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.
Enumerate every unique tag used across the vault along with the number of notes each tag appears in. Detects tags from both inline #hashtags and YAML frontmatter, normalizes them case-insensitively, and returns a sorted list plus the total unique tag count. Use to build a tag cloud, pick categories, audit taxonomy, or discover available tags before calling search_by_tag. 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 list_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 Mcp Pro. Nothing to install.
list_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 list_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 list_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.
list_tags 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.