reload_project
Rescan the project filesystem for new or changed files
This record as markdown: /tools/keeveeg-godot-mcp/reload-project.md
What reload_project does on Godot
AI agents invoke reload_project to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why reload_project is rated High
Rescanning the filesystem triggers an active operation (a filesystem scan and project reload) rather than simply reading data passively. It can cause side effects such as reimporting assets, refreshing project state, and potentially triggering import pipelines. This makes it an Execute-category action rather than a pure Read.
From the tool's definition reload_project / Rescan the project filesystem for new or changed files
Attacks that exploit this kind of access
The rule that runs reload_project 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 reload_project, this is the rule to start with:
reload_project stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 reload_project call is checked against it from then on.
Questions about reload_project
Rescan the project filesystem for new or changed files. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot MCP server in PolicyLayer and add a rule for reload_project: 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.
reload_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reload_project 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 reload_project. 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.
reload_project 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.
Across the catalogue