This record as markdown: /tools/keeveeg-godot-mcp/get-filesystem-tree.md
What get_filesystem_tree does on Godot
AI agents call get_filesystem_tree 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 | string | Yes | Root path to list from (e.g. 'res://') |
filters | array | — | Array of file extensions to filter (e.g. ['gd', 'tscn']) |
max_depth | integer | — | Maximum recursion depth (default: 10) |
Parameters from the server's own tool schema.
Why get_filesystem_tree is rated Low
This tool queries and returns the filesystem structure of a Godot project. It performs a read-only operation that retrieves information about the project's file hierarchy without creating, modifying, deleting, or executing any code. The verb 'Get' combined with a passive data retrieval confirms this is a Read category tool with low severity.
From the tool's definition Tool name 'get_filesystem_tree' and description 'Get the project filesystem tree structure' indicate a retrieval operation with no modification or side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_filesystem_tree 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 get_filesystem_tree, this is the rule to start with:
get_filesystem_tree 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 get_filesystem_tree call is checked against it from then on.
Questions about get_filesystem_tree
Get the project filesystem tree structure. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_filesystem_tree accepts 3 parameters: path, filters, max_depth. Required: path. 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 get_filesystem_tree: 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.
get_filesystem_tree 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 get_filesystem_tree 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 get_filesystem_tree. 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.
get_filesystem_tree is provided by the Godot MCP server (@keeveeg/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