fs_search
Searches for files and folders by name (case-insensitive, partial match) starting from a root directory. Defaults to the home directory. Returns matching items with path, type, and size.
This record as markdown: /tools/com-local-mcp-local-mcp/fs-search.md
What fs_search does on Local
AI agents call fs_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 |
|---|---|---|---|
root | string | — | Root directory to search from. Defaults to home directory (~). |
query | string | Yes | Filename pattern to search for (partial, case-insensitive) |
file_type | string | — | Filter by extension, e.g. 'pdf', 'docx', 'xlsx'. Omit for all types. |
max_results | integer | — | Maximum number of results to return. Default 50, max 200. |
Parameters from the server's own tool schema.
Why fs_search is rated Low
fs_search performs a filesystem search operation that retrieves and lists file/folder metadata without side effects. It matches the 'Read' category pattern (search, list, fetch). Although it provides local filesystem access, the search-only nature limits immediate blast radius. Severity is low because the tool cannot modify, delete, or execute anything—only discover files.
From the tool's definition Tool 'searches for files and folders by name' and 'returns matching items with path, type, and size' — read-only query with no modification or deletion.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs fs_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 fs_search, this is the rule to start with:
fs_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 fs_search call is checked against it from then on.
Questions about fs_search
Searches for files and folders by name (case-insensitive, partial match) starting from a root directory. Defaults to the home directory. Returns matching items with path, type, and size. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
fs_search accepts 4 parameters: root, query, file_type, max_results. 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 fs_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.
fs_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 fs_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 fs_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.
fs_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