finder_list
Lists files and folders at any absolute path (Spotlight-free directory listing, including outside the home folder). For sandboxed reads under the user's home, prefer fs_list.
This record as markdown: /tools/com-local-mcp-local-mcp/finder-list.md
What finder_list does on Local
AI agents call finder_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 list (default: ~) |
limit | integer | — | Max items (default 100) |
Parameters from the server's own tool schema.
Why finder_list is rated Low
This tool performs a read-only operation that retrieves file and folder metadata from the filesystem. It has no side effects—it neither modifies, deletes, nor executes code. The severity is low because directory listing is a basic filesystem operation with minimal blast radius; the worst case is information disclosure of directory contents.
From the tool's definition Tool name 'finder_list' and description explicitly states it 'Lists files and folders at any absolute path' with no modification or deletion capability. The description distinguishes it as a 'directory listing' operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs finder_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 finder_list, this is the rule to start with:
finder_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 finder_list call is checked against it from then on.
Questions about finder_list
Lists files and folders at any absolute path (Spotlight-free directory listing, including outside the home folder). For sandboxed reads under the user's home, prefer fs_list. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
finder_list accepts 2 parameters: path, limit. 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 finder_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.
finder_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 finder_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 finder_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.
finder_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