Lists all files and directories in the root directory of your Obsidian vault
AI agents call list_files_in_vault to retrieve information from MCP server for Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the structure of an Obsidian vault and returns directory/file listings. It has no side effects, does not modify data, and does not execute code or trigger external operations. It is a straightforward read operation with minimal risk even if misused by an agent (worst case: the agent learns what files exist in the vault).
From the tool's definition Tool name is 'list_files_in_vault' and description states it 'Lists all files and directories' — a retrieval operation with no modification or execution.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access list_files_in_vault gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP server for Obsidian, and nothing reaches the server without passing your rules. This is the rule we recommend for list_files_in_vault:
{
"version": "1",
"default": "deny",
"tools": {
"list_files_in_vault": {}
}
}list_files_in_vault is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all files and directories in the root directory of your Obsidian vault. It is categorised as a Read tool in the MCP server for Obsidian MCP Server, which means it retrieves data without modifying state.
Register the MCP server for Obsidian MCP server in PolicyLayer and add a rule for list_files_in_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 MCP server for Obsidian. Nothing to install.
list_files_in_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_files_in_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_files_in_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_files_in_vault is provided by the MCP server for Obsidian MCP server (markuspfundstein/mcp-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP server for Obsidian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 MCP server for Obsidian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.