search_file_contents
AI agents call search_file_contents 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 and searches file contents using regex patterns—a read-only operation with no side effects. It does not write, delete, execute code, or perform financial transactions. The only risk is potential information disclosure if sensitive files are accessible, but the capability itself is a Read operation. Low severity because impact depends entirely on what files exist in the accessible paths.
From the tool's definition Server enables 'regex-based file name and content searches' and 'reading text, PDF, and DOCX files.' The tool name 'search_file_contents' and its placement among sibling tools (list_file_paths, read_files, get_path_type) indicates it queries file contents…
Attacks that exploit this kind of access
search_file_contents. 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_contents: 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_contents 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_contents 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_contents. 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_contents 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 →