This record as markdown: /tools/io-github-kivanccakmak-yaver/tree-dir.md
What tree_dir does on Yaver
AI agents call tree_dir 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 |
|---|---|---|---|
depth | integer | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why tree_dir is rated Low
This tool performs a passive, read-only operation (directory listing). It retrieves and displays file system information with no side effects, no code execution, and no data modification. This is a standard file browsing operation with minimal risk.
From the tool's definition Tool name 'tree_dir' with description 'Show directory tree' indicates a retrieval operation that lists directory structure without modifying, deleting, or executing code.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs tree_dir 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_dir, this is the rule to start with:
tree_dir is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every tree_dir call is checked against it from then on.
Questions about tree_dir
Show directory tree. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
tree_dir accepts 2 parameters: depth, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for tree_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 Yaver. Nothing to install.
tree_dir 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 tree_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.
Set action: deny in the PolicyLayer policy for tree_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.
tree_dir 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue