Search for files by name, content, or metadata
AI agents call search_files to retrieve information from MCP File Browser Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves file information but does not create, modify, delete, or execute anything. It has no side effects beyond data retrieval. Low severity because search operations have minimal blast radius even if misused - an agent could discover sensitive files but cannot access, modify, or delete them without additional tools.
From the tool's definition Tool is described as 'Search for files by name, content, or metadata' - a query operation that retrieves information without modification. Sibling tools (check_permissions, get_file_metadata, list_directory, read_file) are all read-only operations.
Attacks that exploit this kind of access
Search for files by name, content, or metadata. It is categorised as a Read tool in the MCP File Browser Server MCP Server, which means it retrieves data without modifying state.
Register the MCP File Browser Server MCP server in PolicyLayer and add a rule for search_files: 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 MCP File Browser Server. Nothing to install.
search_files 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_files 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_files. 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_files is provided by the MCP File Browser Server MCP server (ntufar/mcp). 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 →