Find local files by name, extension, size, or modification time — metadata only. Use localSearchCode to search file contents. Use the returned paths as inputs to localGetFileContent or LSP tools.
AI agents call localFindFiles to retrieve information from Octocode MCP - AI Context Platform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
queries | array | Yes | Array of queries for localFindFiles. Maximum is 5 queries per call. Multiple queries run in parallel. Use the per-query `page` field to navigate through results |
Parameters from the server's own tool schema.
This tool only retrieves file system metadata without accessing file contents or performing any modifications. It functions as a directory/file discovery mechanism with zero side effects, making it a straightforward Read category tool with low severity.
From the tool's definition Tool returns 'metadata only' about files (name, extension, size, modification time). Description explicitly directs to other tools (localSearchCode, localGetFileContent) for actual data access. No write, execute, delete, or financial operations possible.
Risk signalsAccepts file system path (queries[].path) · High parameter count (32 properties)
Documented attack patterns abuse exactly the kind of access localFindFiles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octocode MCP - AI Context Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for localFindFiles:
{
"version": "1",
"default": "deny",
"tools": {
"localFindFiles": {}
}
}localFindFiles 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 local files by name, extension, size, or modification time — metadata only. Use localSearchCode to search file contents. Use the returned paths as inputs to localGetFileContent or LSP tools. It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.
localFindFiles accepts 1 parameter: queries. Required: queries. The full parameter table on this page comes from the server's own tool schema.
Register the Octocode MCP - AI Context Platform MCP server in PolicyLayer and add a rule for localFindFiles: 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 Octocode MCP - AI Context Platform. Nothing to install.
localFindFiles 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 localFindFiles 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 localFindFiles. 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.
localFindFiles is provided by the Octocode MCP - AI Context Platform MCP server (octocode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octocode MCP - AI Context Platform, 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.
13 Octocode MCP - AI Context Platform tools catalogued and risk-classified — across an index of 43,000+ MCP servers.