search_files
Recursively search for files and directories matching a pattern. The patterns should be glob-style patterns that match paths relative to the working directory. Use pattern like '*.ext' to match files in current directory, and '/*.ext' to match files in all subdirectories. Returns full paths to al...
This record as markdown: /tools/filesystem/search-files.md
What search_files does on Filesystem
AI agents call search_files to retrieve information from Filesystem 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 | Yes | |
pattern | string | Yes | |
excludePatterns | array | — |
Parameters from the server's own tool schema.
Why search_files is rated Low
This tool retrieves metadata about files and directories matching a glob pattern. It performs no write, delete, or execute operations. The blast radius of misuse is minimal—an agent could enumerate the filesystem structure but cannot modify, execute, or access file contents directly. This is a classic Read operation.
From the tool's definition Tool description states it "Recursively search for files and directories matching a pattern" and "Returns full paths to all matching items." The verb 'search' combined with 'returns' indicates data retrieval with no modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs search_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Filesystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_files, this is the rule to start with:
search_files 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 Filesystem, apply this rule, and every search_files call is checked against it from then on.
Questions about search_files
Recursively search for files and directories matching a pattern. The patterns should be glob-style patterns that match paths relative to the working directory. Use pattern like '*.ext' to match files in current directory, and '/*.ext' to match files in all subdirectories. Returns full paths to all matching items. Great for finding files when you don't know their exact location. Only searches within allowed directories. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.
search_files accepts 3 parameters: path, pattern, excludePatterns. Required: path, pattern. The full parameter table on this page comes from the server's own tool schema.
Register the Filesystem MCP server in PolicyLayer and add a rule for search_files: 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 Filesystem. Nothing to install.
search_files 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 search_files 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 search_files. 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.
search_files is provided by the Filesystem MCP server (@modelcontextprotocol/server-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Filesystem, and thousands of servers like it.
This server
Across the catalogue