This record as markdown: /tools/io-github-kivanccakmak-yaver/find-large-files.md
What find_large_files does on Yaver
AI agents call find_large_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 |
|---|---|---|---|
size_mb | integer | — | Min size in MB (default: 100) |
directory | string | — |
Parameters from the server's own tool schema.
Why find_large_files is rated Low
This tool queries the filesystem to locate large files and returns results. It has no side effects—it does not create, modify, delete, or execute anything. It is a pure read operation that retrieves data about file sizes and locations.
From the tool's definition Tool name is 'find_large_files' and description states 'Find large files.' The verb 'find' indicates a search/query operation that retrieves information about files without modifying, executing, or deleting them.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs find_large_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 find_large_files, this is the rule to start with:
find_large_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 find_large_files call is checked against it from then on.
Questions about find_large_files
find_large_files is a read tool on the Yaver MCP server. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
find_large_files accepts 2 parameters: size_mb, directory. 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 find_large_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.
find_large_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 find_large_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 find_large_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.
find_large_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