List available Obsidian vaults
AI agents call list_vaults to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only discovery operation to enumerate available Obsidian vaults. It has no side effects, creates no data, executes no code, and cannot delete or modify anything. The blast radius of misuse is minimal—an attacker gains only knowledge of which vaults exist on the system, not access to their contents (which would require separate tools like read_note).
From the tool's definition Tool name 'list_vaults' and description 'List available Obsidian vaults' indicate a query/enumeration operation that retrieves information about existing vaults without modifying them.
Attacks that exploit this kind of access
List available Obsidian vaults. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for list_vaults: 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 Server. Nothing to install.
list_vaults 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_vaults 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_vaults. 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_vaults is provided by the Obsidian MCP Server MCP server (quinny1187/obsidian-mcp). 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 →