fs_list
Lists files and folders in a local directory. Defaults to the user's home directory. Returns name, path, type (file/directory), size, and modification date for each item. Sorted: directories first, then files, both alphabetically.
This record as markdown: /tools/com-local-mcp-local-mcp/fs-list.md
What fs_list does on Local
AI agents call fs_list to retrieve information from Local 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 | — | Absolute path to the directory. Defaults to the home directory (~) if omitted. |
show_hidden | boolean | — | Include hidden files (starting with '.'). Default false. |
Parameters from the server's own tool schema.
Why fs_list is rated Low
fs_list performs directory enumeration and metadata retrieval without creating, modifying, deleting, or executing anything. It is a pure query operation that retrieves filesystem information. The severity is low because directory listings alone pose minimal risk unless the AI agent subsequently abuses the data to access sensitive files—but that would be a separate tool's responsibility.
From the tool's definition Tool description states it 'Lists files and folders in a local directory' and 'Returns name, path, type (file/directory), size, and modification date'. These are read-only retrieval operations with no side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs fs_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fs_list, this is the rule to start with:
fs_list 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 Local, apply this rule, and every fs_list call is checked against it from then on.
Questions about fs_list
Lists files and folders in a local directory. Defaults to the user's home directory. Returns name, path, type (file/directory), size, and modification date for each item. Sorted: directories first, then files, both alphabetically. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
fs_list accepts 2 parameters: path, show_hidden. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for fs_list: 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 Local. Nothing to install.
fs_list 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 fs_list 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 fs_list. 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.
fs_list is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue