AI agents call search_files to retrieve information from Everything without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries file system data via Windows Everything SDK. No modification, deletion, execution, or financial capability is implied. Even with empty description, the context of sibling search tools and server purpose clearly indicates this is a read operation with low severity.
From the tool's definition Tool name 'search_files' combined with server description stating 'file searches' and sibling tools 'search_content', 'search_files_advanced', 'find_duplicates' all indicate read-only query operations.
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 Everything, 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 Everything MCP Server, which means it retrieves data without modifying state.
Register the Everything 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 Everything. 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 Everything MCP server (peterparker57/everything-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Everything, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Everything tools catalogued and risk-classified — across an index of 43,000+ MCP servers.