Low Risk

search_files_advanced

search_files_advanced

How to control search_files_advanced ↓

What search_files_advanced does on Everything

AI agents call search_files_advanced 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.

Low Risk

Why search_files_advanced needs a policy

File searching retrieves data without modifying, deleting, or executing anything. The tool queries a local search index to return matching files, which is a read-only operation. No side effects occur. Severity is low because search operations have minimal blast radius—they cannot damage data, execute code, or cause financial harm.

From the tool's definition Tool name is 'search_files_advanced' and belongs to a file search server ('Enables instant file searches on Windows'). The sibling tools 'search_files' and 'search_content' are clearly read-only search operations. Descriptions confirm 'search' functionality.

Documented attack patterns abuse exactly the kind of access search_files_advanced gives an agent:

How to control search_files_advanced

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_advanced:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_files_advanced": {}
  }
}

search_files_advanced is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Everything — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_files_advanced

What does the search_files_advanced tool do? +

search_files_advanced. It is categorised as a Read tool in the Everything MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_files_advanced? +

Register the Everything MCP server in PolicyLayer and add a rule for search_files_advanced: 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.

What risk level is search_files_advanced? +

search_files_advanced is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_files_advanced? +

Yes. Add a rate_limit block to the search_files_advanced 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.

How do I block search_files_advanced completely? +

Set action: deny in the PolicyLayer policy for search_files_advanced. 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.

What MCP server provides search_files_advanced? +

search_files_advanced 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.

Enforce policy on every Everything tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.