Find files in the workspace without dropping to the shell.
AI agents call find_files to retrieve information from Vigentic MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs file discovery and listing within the workspace, which is a read-only operation with no side effects. It does not modify, execute, delete, or financially impact any resources. The explicit contrast with shell operations reinforces that this is a safe query function. Severity is low because misuse would only expose file structure information.
From the tool's definition Tool name 'find_files' and description 'Find files in the workspace without dropping to the shell' indicate a search/query operation that retrieves file information. The phrase 'without dropping to the shell' emphasizes it is a safe, non-executable operation.
Attacks that exploit this kind of access
Find files in the workspace without dropping to the shell. It is categorised as a Read tool in the Vigentic MCP MCP Server, which means it retrieves data without modifying state.
Register the Vigentic 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 Vigentic MCP. 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 Vigentic MCP server (munozu/vigentic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
find_files is one line of Vigentic's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →