Get a recursive tree view of files and directories as a JSON structure.
AI agents call directory_tree to retrieve information from Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays directory structure information in a read-only manner. It performs a query operation ('Get') that returns data about the file system without creating, modifying, deleting, or executing anything. The severity is low because directory listing is generally non-sensitive metadata that poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'directory_tree' and description 'Get a recursive tree view of files and directories as a JSON structure' indicate retrieval of directory/file metadata with no modification capability.
Documented attack patterns abuse exactly the kind of access directory_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Search, and nothing reaches the server without passing your rules. This is the rule we recommend for directory_tree:
{
"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.
Free to start. No card required.
Get a recursive tree view of files and directories as a JSON structure. It is categorised as a Read tool in the Search MCP Server, which means it retrieves data without modifying state.
Register the Search 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 Search. Nothing to install.
directory_tree 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 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.
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.
directory_tree is provided by the Search MCP server (@agent-infra/mcp-server-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Search, 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.
36 Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.