editor_list_filesystem
List files and directories in the editor filesystem.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-list-filesystem.md
What editor_list_filesystem does on Godot
AI agents call editor_list_filesystem 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 | — | Directory path |
pattern | object | — | Glob pattern (e.g. "*.gd") |
recursive | object | — |
Parameters from the server's own tool schema.
Why editor_list_filesystem is rated Low
This tool queries and returns filesystem information from the Godot editor without modifying, deleting, or executing any code. It is a read-only operation analogous to 'list' or 'fetch' operations. The low severity reflects minimal blast radius—an agent cannot damage assets or systems by listing files.
From the tool's definition Tool name 'editor_list_filesystem' and description 'List files and directories in the editor filesystem' indicate a retrieval operation with no side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_list_filesystem 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 editor_list_filesystem, this is the rule to start with:
editor_list_filesystem 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 editor_list_filesystem call is checked against it from then on.
Questions about editor_list_filesystem
List files and directories in the editor filesystem. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
editor_list_filesystem 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 editor_list_filesystem: 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.
editor_list_filesystem 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 editor_list_filesystem 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 editor_list_filesystem. 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.
editor_list_filesystem 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