linux_file_finder
AI agents call linux_file_finder to retrieve information from Velociraptor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
File finder tools typically retrieve or query filesystem metadata without modifying data, placing them in the Read category. Severity is medium rather than low because finding files across a system could help an agent locate sensitive data, configuration files, or evidence during unauthorized reconnaissance.
From the tool's definition Tool name 'linux_file_finder' suggests file search/discovery functionality. No description provided, but based on naming convention and sibling tools (collect_file, collect_artifact), this appears to be a query/search operation on Linux systems.
Attacks that exploit this kind of access
linux_file_finder. It is categorised as a Read tool in the Velociraptor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Velociraptor MCP Server MCP server in PolicyLayer and add a rule for linux_file_finder: 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 Velociraptor MCP Server. Nothing to install.
linux_file_finder 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 linux_file_finder 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 linux_file_finder. 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.
linux_file_finder is provided by the Velociraptor MCP Server MCP server (snoe-findley/mcp-velociraptor). 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 →