list_dir

List a directory inside the pre-patch source repo (path relative to repo root).

SERVER0sec SOURCE0sec-labs/0sec

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0sec/list-dir.md

WHAT IT DOES

What list_dir does on 0sec

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

RISK

Why list_dir is rated Low

Even though list_dir only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_dir safely

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

list_dir Allowed

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

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

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

FAQ

Questions about list_dir

What does the list_dir tool do? +

List a directory inside the pre-patch source repo (path relative to repo root). It is categorised as a Read tool in the 0sec MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_dir? +

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

What risk level is list_dir? +

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

Can I rate-limit list_dir? +

Yes. Add a rate_limit block to the list_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.

How do I block list_dir completely? +

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

What MCP server provides list_dir? +

list_dir is provided by the 0sec MCP server (0sec-labs/0sec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0sec, and thousands of servers like it.

This server

All 31 0sec 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 →