Low Risk

search_files_by_name

Recursively search for files and directories matching a pattern.

How to control search_files_by_name ↓

What search_files_by_name does on Filesystem MCP Server for WSL

AI agents call search_files_by_name to retrieve information from Filesystem MCP Server for WSL 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_by_name needs a policy

The tool retrieves metadata about files and directories matching search criteria without modifying, deleting, or executing any filesystem changes. Search is fundamentally a read operation. Low severity because it only exposes file paths and names, not contents, and has minimal blast radius for misuse.

From the tool's definition Tool description states 'Recursively search for files and directories matching a pattern' — a read-only query operation with no side effects.

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

How to control search_files_by_name

PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem MCP Server for WSL, and nothing reaches the server without passing your rules. This is the rule we recommend for search_files_by_name:

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

search_files_by_name 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 Filesystem MCP Server for WSL — 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_by_name

What does the search_files_by_name tool do? +

Recursively search for files and directories matching a pattern. It is categorised as a Read tool in the Filesystem MCP Server for WSL MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_files_by_name? +

Register the Filesystem MCP Server for WSL MCP server in PolicyLayer and add a rule for search_files_by_name: 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 Filesystem MCP Server for WSL. Nothing to install.

What risk level is search_files_by_name? +

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

Can I rate-limit search_files_by_name? +

Yes. Add a rate_limit block to the search_files_by_name 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_by_name completely? +

Set action: deny in the PolicyLayer policy for search_files_by_name. 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_by_name? +

search_files_by_name is provided by the Filesystem MCP Server for WSL MCP server (webconsulting/mcp-server-wsl-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem MCP Server for WSL tool call.

Start from Filesystem MCP Server for WSL, 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.

14 Filesystem MCP Server for WSL 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.