Find files by name (substring). If content=True, also greps text files for the query.
AI agents call find_file to retrieve information from Nexus Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
find_file retrieves information about files and optionally their contents via grep. This is a read-only operation with no side effects. Even with content search enabled, the tool only queries and returns data without altering, deleting, or executing anything. The blast radius of misuse is low—worst case is unauthorized information disclosure within already-accessible files on the host system.
From the tool's definition Tool description: 'Find files by name (substring). If content=True, also greps text files for the query.' The tool performs search and retrieval operations only—substring matching on filenames and optional text grep of file contents.
Attacks that exploit this kind of access
Find files by name (substring). If content=True, also greps text files for the query. It is categorised as a Read tool in the Nexus Core MCP Server, which means it retrieves data without modifying state.
Register the Nexus Core MCP server in PolicyLayer and add a rule for find_file: 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 Nexus Core. Nothing to install.
find_file 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 find_file 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 find_file. 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.
find_file is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →