AI agents call search_files to retrieve information from MCP Filesystem Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_files most likely retrieves or locates files matching criteria within the filesystem, consistent with the server's intelligence-focused and read-only nature. No evidence suggests it modifies, deletes, or executes arbitrary code. Confidence is slightly reduced due to empty description, but context from sibling tools strongly indicates a Read classification.
From the tool's definition Tool name 'search_files' indicates a query/search operation. Description is empty, but the sibling tools on the filesystem server (calculate_directory_size, directory_tree, get_file_info, find_duplicate_files, find_empty_directories, find_large_files) are all…
Documented attack patterns abuse exactly the kind of access search_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Filesystem Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_files:
{
"version": "1",
"default": "deny",
"tools": {
"search_files": {}
}
}search_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_files. It is categorised as a Read tool in the MCP Filesystem Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Filesystem Server 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 MCP Filesystem Server. 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 MCP Filesystem Server MCP server (safurrier/mcp-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 MCP Filesystem Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 MCP Filesystem Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.