search_files
Recursively search for files and directories matching a pattern
This record as markdown: /tools/deep-ai-kr-dev-mcp/search-files.md
What search_files does on Dev
AI agents call search_files to retrieve information from Dev 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 | — | Directory to search in (relative to root) |
pattern | string | — | Search pattern (case-insensitive, matches partial names) |
Parameters from the server's own tool schema.
Why search_files is rated Low
search_files queries the filesystem to locate files matching criteria. It has no side effects, does not modify data, execute code, or delete anything. It falls squarely under Read (retrieve/query data). The configurable root restriction further limits blast radius to low severity.
From the tool's definition Tool description states 'Recursively search for files and directories matching a pattern' — a read-only operation that retrieves metadata without modifying or executing anything.
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 Dev, 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 Dev, 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. It is categorised as a Read tool in the Dev MCP Server, which means it retrieves data without modifying state.
search_files accepts 2 parameters: path, pattern. The full parameter table on this page comes from the server's own tool schema.
Register the Dev 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 Dev. 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 Dev MCP server (deep-ai-kr/dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dev, and thousands of servers like it.
This server
Across the catalogue