This record as markdown: /tools/yanhuifair-godot-mcp/list-projects.md
What list_projects does on Godot
AI agents call list_projects 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 |
|---|---|---|---|
directory | object | — | Directory to search (default: current directory) |
recursive | object | — | Search recursively (default: true) |
Parameters from the server's own tool schema.
Why list_projects is rated Low
This tool performs a directory scan and lists Godot projects, which is a read-only retrieval operation with no side effects. It gathers and returns information but does not create, modify, delete, or execute any operations. The low severity reflects that misuse would only expose file system structure information about Godot projects.
From the tool's definition Tool name is 'list_projects' and description states it will 'Scan directory for Godot projects' — a query operation that retrieves information about existing projects without modifying anything.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs list_projects 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_projects, this is the rule to start with:
list_projects 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_projects call is checked against it from then on.
Questions about list_projects
Scan directory for Godot projects. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
list_projects accepts 2 parameters: directory, 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_projects: 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_projects 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_projects 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_projects. 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_projects 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