search_by_filename_regex

Search for files and directories using regex pattern on filenames

Server LocalFS MCP Server mcp-bridge/local-filesystem
Category Read
Risk class Low
Parameters 00 required

What search_by_filename_regex does on LocalFS MCP Server

AI agents call search_by_filename_regex to retrieve information from LocalFS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_by_filename_regex needs a policy

This is a read-only search operation that retrieves and queries filesystem metadata. While the sibling tools include destructive operations (delete_file, delete_directory), this specific tool only searches and returns results. The regex pattern matching on filenames poses minimal risk as it cannot modify, execute, or delete data—only discover it.

From the tool's definition Tool performs pattern matching to locate files and directories with no modification capability. The description explicitly states it "search[es] for files and directories using regex pattern on filenames" with no mention of creating, modifying, or deleting…

Questions about search_by_filename_regex

What does the search_by_filename_regex tool do? +

Search for files and directories using regex pattern on filenames. It is categorised as a Read tool in the LocalFS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_filename_regex? +

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

What risk level is search_by_filename_regex? +

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

Can I rate-limit search_by_filename_regex? +

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

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

search_by_filename_regex is provided by the LocalFS MCP Server MCP server (mcp-bridge/local-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.