tree

Show directory tree (auto-excludes node_modules, .git, etc.).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/tree.md

WHAT IT DOES

What tree does on Yaver

AI agents call tree to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`all`	boolean	—	Show hidden files
`path`	string	—
`depth`	integer	—	Max depth (default: 3)
`dirs_only`	boolean	—

Parameters from the server's own tool schema.

RISK

Why tree is rated Low

This tool only displays information about the directory structure without creating, modifying, deleting, executing code, or triggering external operations. It is a passive inspection tool with no side effects, fitting the Read category.

From the tool's definition Tool name 'tree' and description 'Show directory tree (auto-excludes node_modules, .git, etc.)' indicates read-only retrieval of file system directory structure with no modifications or deletions.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tree safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tree, this is the rule to start with:

tree Allowed

tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tree": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every tree call is checked against it from then on.

FAQ

Questions about tree

What does the tree tool do? +

Show directory tree (auto-excludes node_modules, .git, etc.). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does tree accept? +

tree accepts 4 parameters: all, path, depth, dirs_only. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tree? +

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

What risk level is tree? +

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

Can I rate-limit tree? +

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

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

tree is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →