Get all tags used in the vault
AI agents call get_tags to retrieve information from ObsidianReaderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists tag metadata from an Obsidian vault without modifying, deleting, or executing any operations. It is a straightforward read operation analogous to list or query functions. Low severity because exposing tag information carries minimal risk unless the vault contains highly sensitive metadata, which is unlikely for most use cases.
From the tool's definition Tool named 'get_tags' with description 'Get all tags used in the vault' — a retrieval operation with no side effects that queries existing metadata.
Attacks that exploit this kind of access
Get all tags used in the vault. It is categorised as a Read tool in the ObsidianReaderMCP MCP Server, which means it retrieves data without modifying state.
Register the ObsidianReader 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 ObsidianReaderMCP. 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 ObsidianReader MCP server (qianjue-cn/obsidianreadermcp). 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 →