Low Risk

directory_tree

Get a recursive tree view of files and directories as a JSON structure.

How to control directory_tree ↓

What directory_tree does on Filesystem MCP Server SSE

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

Low Risk

Why directory_tree needs a policy

This tool retrieves metadata about the filesystem hierarchy in a structured format. It performs no write, delete, execute, or financial operations. The recursive tree view is informational only, with no side effects on the filesystem. Consistent with sibling 'Read' category tools like 'list_directory', 'read_file', and 'get_file_info' on this server.

From the tool's definition Tool name 'directory_tree' and description 'Get a recursive tree view of files and directories as a JSON structure' indicates a read-only operation that retrieves and displays directory structure without modification.

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

How to control directory_tree

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

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

directory_tree 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 Filesystem MCP Server SSE — 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 directory_tree

What does the directory_tree tool do? +

Get a recursive tree view of files and directories as a JSON structure. It is categorised as a Read tool in the Filesystem MCP Server SSE MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on directory_tree? +

Register the Filesystem MCP Server SSE MCP server in PolicyLayer and add a rule for directory_tree: 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 Filesystem MCP Server SSE. Nothing to install.

What risk level is directory_tree? +

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

Can I rate-limit directory_tree? +

Yes. Add a rate_limit block to the directory_tree 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 directory_tree completely? +

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

directory_tree is provided by the Filesystem MCP Server SSE MCP server (ysthink/filesystem-mcp-server-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem MCP Server SSE tool call.

Start from Filesystem MCP Server SSE, 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.

11 Filesystem MCP Server SSE 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.