finder_search
Searches for files by name anywhere on the filesystem (uses mdfind/Spotlight).
This record as markdown: /tools/com-local-mcp-local-mcp/finder-search.md
What finder_search does on Local
AI agents call finder_search 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 | — | Limit search to this directory (optional) |
limit | integer | — | Max results (default 50) |
query | string | Yes | Filename or content to search for |
Parameters from the server's own tool schema.
Why finder_search is rated Low
This tool retrieves filesystem data through searches and has no side effects—it does not create, modify, delete, or execute code. However, the severity is elevated to 'medium' rather than 'low' because unrestricted file searching could expose sensitive user data (credentials, personal documents, health records) if an AI agent conducts broad searches without proper filtering, especially on a system containing Mail,…
From the tool's definition Tool description states it 'Searches for files by name' using Spotlight, which is a search/query operation with no modification or deletion capability.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs finder_search 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_search, this is the rule to start with:
finder_search 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_search call is checked against it from then on.
Questions about finder_search
Searches for files by name anywhere on the filesystem (uses mdfind/Spotlight). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
finder_search accepts 3 parameters: path, limit, query. Required: query. 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_search: 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_search 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_search 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_search. 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_search 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