search_file_name
AI agents call search_file_name to retrieve information from File Search Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries file system metadata (file names matching search criteria) without side effects. It does not create, modify, delete, or execute anything. While the tool description is empty, the name and server context make the intent clear: it performs a read-only search operation.
From the tool's definition Tool is part of a file system search and inspection server; sibling tools include 'search_file_contents', 'list_file_paths', and 'read_files' which are all read-only operations.
Attacks that exploit this kind of access
search_file_name. It is categorised as a Read tool in the File Search Tool MCP Server, which means it retrieves data without modifying state.
Register the File Search Tool MCP server in PolicyLayer and add a rule for search_file_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 File Search Tool. Nothing to install.
search_file_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_file_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_file_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_file_name is provided by the File Search Tool MCP server (rjtpp/mcp-server-file-search-tool). 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 →