list_project_files
List files and directories in the Godot project.
This record as markdown: /tools/yanhuifair-godot-mcp/list-project-files.md
What list_project_files does on Godot
AI agents call list_project_files to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | object | — | Subdirectory relative to project root (default: root) |
pattern | object | — | Glob pattern filter (e.g. "*.tscn") |
recursive | object | — | Recurse into subdirectories (default: true) |
Parameters from the server's own tool schema.
Why list_project_files is rated Low
This tool retrieves information about the project's file structure without modifying, executing, or deleting anything. It is a non-destructive read operation with minimal risk even if misused by an AI agent, as listing files does not alter system state or trigger external operations.
From the tool's definition Tool name 'list_project_files' and description 'List files and directories in the Godot project' indicate a query/retrieval operation with no side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs list_project_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_project_files, this is the rule to start with:
list_project_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 Godot, apply this rule, and every list_project_files call is checked against it from then on.
Questions about list_project_files
List files and directories in the Godot project. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
list_project_files accepts 3 parameters: path, pattern, recursive. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for list_project_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 Godot. Nothing to install.
list_project_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_project_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_project_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_project_files is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue