List the contents of a directory using an absolute path. Returns a formatted list showing files and subdirectories with clear [FILE]/[DIR] indicators. Useful for exploring project structure and understanding codebase organization.
AI agents call file_system_read_directory to retrieve information from Repomix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves directory metadata and structure without creating, modifying, deleting, or executing anything. It is a straightforward directory listing operation analogous to 'ls' or 'dir' commands, which are classified as Read operations.
From the tool's definition Tool description states it "List the contents of a directory" and is explicitly "Useful for exploring project structure". The [FILE]/[DIR] indicators show it returns directory listing information with no modification capability.
Documented attack patterns abuse exactly the kind of access file_system_read_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Repomix, and nothing reaches the server without passing your rules. This is the rule we recommend for file_system_read_directory:
{
"version": "1",
"default": "deny",
"tools": {
"file_system_read_directory": {}
}
}file_system_read_directory 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.
List the contents of a directory using an absolute path. Returns a formatted list showing files and subdirectories with clear [FILE]/[DIR] indicators. Useful for exploring project structure and understanding codebase organization. It is categorised as a Read tool in the Repomix MCP Server, which means it retrieves data without modifying state.
Register the Repomix MCP server in PolicyLayer and add a rule for file_system_read_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 Repomix. Nothing to install.
file_system_read_directory 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 file_system_read_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.
Set action: deny in the PolicyLayer policy for file_system_read_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.
file_system_read_directory is provided by the Repomix MCP server (yamadashy/repomix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Repomix tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Repomix tools catalogued and risk-classified — across an index of 42,500+ MCP servers.