find
Finds files and directories using fd with structured output. Returns file paths, names, and extensions.
This record as markdown: /tools/io-github-dave-london-npm/find.md
What find does on Npm
AI agents call find to retrieve information from Npm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why find is rated Low
This tool only retrieves and returns information about files and directories. It has no side effects on the filesystem, does not execute code, does not modify data, and does not delete anything. It is purely a read operation that queries file system metadata.
From the tool's definition Tool "find" with description "Finds files and directories using fd with structured output. Returns file paths, names, and extensions." - performs query/search operations that retrieve directory and file metadata without modification.
Attacks that exploit this kind of access
The rule that runs find safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find, this is the rule to start with:
find is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Npm, apply this rule, and every find call is checked against it from then on.
Questions about find
Finds files and directories using fd with structured output. Returns file paths, names, and extensions. It is categorised as a Read tool in the Npm MCP Server, which means it retrieves data without modifying state.
Register the Npm MCP server in PolicyLayer and add a rule for find: 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 Npm. Nothing to install.
find 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 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. 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 is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue