search_files
Search files using Spotlight (mdfind). Searches file names and content.
This record as markdown: /tools/io-github-heznpc-iconnect/search-files.md
What search_files does on Iconnect
AI agents call search_files to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_files is rated Low
This tool performs read-only file search operations using macOS Spotlight (mdfind). It retrieves and returns matching files and content but does not create, modify, or delete anything. The blast radius of misuse is limited to information disclosure of files already present on the system.
From the tool's definition search_files: Search files using Spotlight (mdfind). Searches file names and content. Returns query results without modifying, creating, or deleting data.
Attacks that exploit this kind of access
The rule that runs search_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_files, this is the rule to start with:
search_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 Iconnect, apply this rule, and every search_files call is checked against it from then on.
Questions about search_files
Search files using Spotlight (mdfind). Searches file names and content. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for search_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 Iconnect. Nothing to install.
search_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 search_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 search_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.
search_files is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue