List all tags used across the vault with their usage counts.
AI agents call list_tags to retrieve information from Mcp Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated metadata (tag inventory and usage statistics) without altering, deleting, or executing anything. It is a pure read operation similar to other Read-category sibling tools like 'get_backlinks', 'get_outlinks', and 'get_orphans'. The blast radius of misuse is minimal—an AI agent cannot cause data loss, financial harm, or unintended code execution via tag enumeration.
From the tool's definition Tool 'list_tags' provides a listing/query function that retrieves and reports tag usage counts across the vault with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
List all tags used across the vault with their usage counts. It is categorised as a Read tool in the Mcp Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Obsidian 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 Mcp Obsidian. 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 Mcp Obsidian MCP server (jkang8/mcp-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →