Find files by name pattern. Returns list of matching file paths. Recursively searches all subdirectories by default.
AI agents call find_files to retrieve information from MCP Local File Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about files matching a pattern without creating, modifying, deleting, or executing anything. It is a pure query/search operation with no side effects. The blast radius is minimal—worst case an agent learns about files that exist on the system, which is informational only.
From the tool's definition Tool performs file system search and returns matching file paths. Description states 'Find files by name pattern. Returns list of matching file paths.' with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Find files by name pattern. Returns list of matching file paths. Recursively searches all subdirectories by default. It is categorised as a Read tool in the MCP Local File Reader MCP Server, which means it retrieves data without modifying state.
Register the MCP Local File Reader MCP server in PolicyLayer and add a rule for find_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 MCP Local File Reader. Nothing to install.
find_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_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_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_files is provided by the MCP Local File Reader MCP server (yryuu/mcp-localfile-all-read). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →