Recursively search for files and directories matching a pattern.
AI agents call search_files to retrieve information from Helm Chart CLI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs filesystem searches and retrieval operations without side effects. It queries file metadata and paths but does not create, modify, delete, execute, or move data. The blast radius of misuse is minimal—an agent could discover sensitive file paths but cannot access contents, modify systems, or trigger external operations.
From the tool's definition Tool name 'search_files' combined with description 'Recursively search for files and directories matching a pattern' indicates read-only file system querying with no modification or execution capabilities.
Attacks that exploit this kind of access
Recursively search for files and directories matching a pattern. It is categorised as a Read tool in the Helm Chart CLI MCP Server, which means it retrieves data without modifying state.
Register the Helm Chart CLI 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 Helm Chart CLI. 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 Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →