List all files in the virtual filesystem. No parameters needed. Returns file paths.
AI agents call list_files to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that enumerates files in a filesystem namespace. It retrieves data (file paths) with no side effects, no code execution, and no modifications to system state. The lack of parameters and the explicit 'Returns file paths' phrasing confirm it is a simple listing/retrieval operation.
From the tool's definition Tool name 'list_files' and description 'List all files in the virtual filesystem. No parameters needed. Returns file paths.' indicate retrieval of directory/file information without modification or execution.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all files in the virtual filesystem. No parameters needed. Returns file paths. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for list_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 Claude Flow. Nothing to install.
list_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 list_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 list_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.
list_files is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.