search_files
Search for files by name pattern in a directory. Uses glob patterns (e.g. '*.go', 'test_*.py'). Skips node_modules, .git, vendor, etc.
This record as markdown: /tools/io-github-kivanccakmak-yaver/search-files.md
What search_files does on Yaver
AI agents call search_files to retrieve information from Yaver 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 |
|---|---|---|---|
pattern | string | Yes | Glob pattern to match filenames (e.g. '*.go', 'README*', '*.test.ts') |
directory | string | — | Directory to search in (default: agent work dir) |
max_results | integer | — | Max results (default: 50) |
Parameters from the server's own tool schema.
Why search_files is rated Low
This tool retrieves information (file names and locations) matching a glob pattern without side effects. It is a read-only operation that performs file system queries similar to standard search utilities. The filtering of node_modules, .git, vendor directories indicates safe defaults for a dev tool. Low severity because file discovery alone has minimal impact without subsequent operations.
From the tool's definition Tool description states 'Search for files by name pattern in a directory' with glob patterns. No modifications, deletions, or execution of files—purely a search/query operation that retrieves file metadata based on pattern matching.
Risk signalsAccepts file system path (directory)
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 Yaver, 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 Yaver, apply this rule, and every search_files call is checked against it from then on.
Questions about search_files
Search for files by name pattern in a directory. Uses glob patterns (e.g. '*.go', 'test_*.py'). Skips node_modules, .git, vendor, etc. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
search_files accepts 3 parameters: pattern, directory, max_results. Required: pattern. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue