Find files matching glob pattern using in-memory index. Supports path patterns (*.py, test_*.js) and filename-only matching (README.md).
AI agents call find_files to retrieve information from Code Index without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only searches and retrieves file metadata matching specified patterns. It has no capability to modify, delete, execute, or move files. No side effects occur from invoking this tool. The blast radius of misuse is minimal—an agent might retrieve unintended file paths but cannot act destructively upon them. This is a straightforward Read operation typical of code indexing and analysis workflows.
From the tool's definition Tool retrieves file information using glob pattern matching against an in-memory index. Key terms: 'Find files', 'using in-memory index', 'glob pattern' indicate a search/query operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access find_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Code Index, and nothing reaches the server without passing your rules. This is the rule we recommend for find_files:
{
"version": "1",
"default": "deny",
"tools": {
"find_files": {}
}
}find_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find files matching glob pattern using in-memory index. Supports path patterns (*.py, test_*.js) and filename-only matching (README.md). It is categorised as a Read tool in the Code Index MCP Server, which means it retrieves data without modifying state.
Register the Code Index MCP server in PolicyLayer and add a rule for find_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 Code Index. Nothing to install.
find_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 find_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 find_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.
find_files is provided by the Code Index MCP server (johnhuang316/code-index-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Code Index, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Code Index tools catalogued and risk-classified — across an index of 43,000+ MCP servers.