Search for files and directories by exact name match
AI agents call search_by_name 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.
This tool only retrieves information about files and directories matching a search criteria. It performs a read-only query operation that does not create, modify, delete, or execute anything. No data is altered and no external operations are triggered. The low severity reflects minimal blast radius even if an AI agent misuses the search - it cannot harm data or systems.
From the tool's definition Tool description states 'Search for files and directories by exact name match' - a query operation with no side effects. The server description confirms it provides 'content search with glob and regex patterns' as part of sandboxed filesystem operations.
Attacks that exploit this kind of access
Search for files and directories by exact name match. It is categorised as a Read tool in the LocalFS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LocalFS MCP Server MCP server in PolicyLayer and add a rule for search_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 LocalFS MCP Server. Nothing to install.
search_by_name 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_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.
Set action: deny in the PolicyLayer policy for search_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.
search_by_name 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.
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 →