AI agents call list_vault to retrieve information from Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about files in the vault with no side effects. It performs a read-only operation similar to 'ls' or 'find'. The severity is low because listing files exposes vault structure but does not modify, execute, or delete anything. Confidence is high due to the clear read-only semantics of 'list' operations.
From the tool's definition Tool name 'list_vault' and description 'List all files in the Obsidian vault' indicate retrieval of directory/file information without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all files in the Obsidian vault. Use. It is categorised as a Read tool in the Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP server in PolicyLayer and add a rule for list_vault: 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. Nothing to install.
list_vault 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_vault 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_vault. 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_vault is provided by the Obsidian MCP server (yanxue06/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 →