list_directory

List files and directories at a path.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What list_directory does on Yaver

AI agents call list_directory 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
`path`	string	—	Directory path (default: work dir)

Parameters from the server's own tool schema.

RISK

Why list_directory is rated Low

This tool only queries and returns information about the filesystem structure without modifying, deleting, or executing anything. It is a straightforward read operation, making it low risk even if misused by an agent (worst case: directory information disclosure).

From the tool's definition Tool name 'list_directory' and description 'List files and directories at a path' indicate a retrieval operation with no side effects.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_directory 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 list_directory, this is the rule to start with:

list_directory Allowed

list_directory 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": {
    "list_directory": {}
  }
}

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 list_directory call is checked against it from then on.

FAQ

Questions about list_directory

What does the list_directory tool do? +

List files and directories at a path. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does list_directory accept? +

list_directory accepts 1 parameter: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_directory? +

Register the Yaver MCP server in PolicyLayer and add a rule for list_directory: 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 list_directory? +

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

Can I rate-limit list_directory? +

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

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

list_directory 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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