lists files and folders within a specified directory in the obsidian vault. if no directory is specified, lists items in the vault root.
AI agents call obsidian_list_files 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 only retrieves and displays the directory structure and file listing from an Obsidian vault. It has no side effects, cannot modify data, execute code, or delete anything. The blast radius of misuse is minimal - an attacker could only enumerate the vault's contents, which is a low-severity information disclosure risk.
From the tool's definition Tool description states it 'lists files and folders within a specified directory' - a pure query operation with no modification or execution capability.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access obsidian_list_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian_list_files:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian_list_files": {}
}
} obsidian_list_files 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 files and folders within a specified directory in the obsidian vault. if no directory is specified, lists items in the vault root. 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 obsidian_list_files: 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.
obsidian_list_files 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 obsidian_list_files 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 obsidian_list_files. 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.
obsidian_list_files is provided by the Obsidian MCP Server MCP server (louis030195/easy-obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, 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.
6 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.