List every tag present in the vault, together with its usage count.
AI agents call list_tags to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only enumeration tool that gathers statistics about existing tags. It has no side effects, creates no data, executes no code, and cannot delete or move anything. The blast radius of misuse is minimal — the worst an agent could do is spam calls to list tags repeatedly or leak knowledge of the vault's tag structure, neither of which causes damage.
From the tool's definition Tool is described as 'List every tag present in the vault, together with its usage count' — a retrieval operation that queries metadata without modifying data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every tag present in the vault, together with its usage count. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified 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 Modified. 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 Modified MCP server (@marwansaab/obsidian-modified-mcp-server). 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 →