Low Risk

list_dir

List subdirectories in a path. Returns only folder names (not files). IMPORTANT: Path must end with / (e.g.,

How to control list_dir ↓

What list_dir does on Obsidian HTTP MCP

AI agents call list_dir to retrieve information from Obsidian HTTP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_dir needs a policy

This tool only queries and returns information about directory structure without creating, modifying, deleting, or executing anything. It is a straightforward read operation analogous to 'ls' in file systems. Low severity because the blast radius of misuse is limited to information disclosure of directory names.

From the tool's definition Tool description states 'List subdirectories in a path. Returns only folder names (not files)' - purely a retrieval/listing operation with no side effects or modifications.

Documented attack patterns abuse exactly the kind of access list_dir gives an agent:

How to control list_dir

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian HTTP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_dir:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_dir": {}
  }
}

list_dir is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Obsidian HTTP MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_dir

What does the list_dir tool do? +

List subdirectories in a path. Returns only folder names (not files). IMPORTANT: Path must end with / (e.g.,. It is categorised as a Read tool in the Obsidian HTTP MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_dir? +

Register the Obsidian HTTP MCP server in PolicyLayer and add a rule for list_dir: 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 HTTP MCP. Nothing to install.

What risk level is list_dir? +

list_dir is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_dir? +

Yes. Add a rate_limit block to the list_dir 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.

How do I block list_dir completely? +

Set action: deny in the PolicyLayer policy for list_dir. 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.

What MCP server provides list_dir? +

list_dir is provided by the Obsidian HTTP MCP server (nasandnora/obsidian-http-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian HTTP MCP tool call.

Start from Obsidian HTTP MCP, 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.

12 Obsidian HTTP MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.