This record as markdown: /tools/ra1nyxin-allcanuse-mcp/find-files.md
What find_files does on Allcanuse
AI agents call find_files to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why find_files is rated Low
File finding is a read-only operation that retrieves file paths and metadata without creating, modifying, deleting, or executing code. Even with path traversal risks in hostile environments, the inherent function is discovery rather than mutation. Confidence is reduced due to absent tool description; a malicious implementation could theoretically do more, but the name strongly suggests read-only behavior.
From the tool's definition Tool name 'find_files' indicates a file search/discovery operation with no modification capability. Description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs find_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_files, this is the rule to start with:
find_files 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 Allcanuse, apply this rule, and every find_files call is checked against it from then on.
Questions about find_files
find_files is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.
Register the Allcanuse 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 Allcanuse. 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 Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Allcanuse, and thousands of servers like it.
This server
Across the catalogue