This record as markdown: /tools/keeveeg-godot-mcp/reorder-autoloads.md
What reorder_autoloads does on Godot
AI agents use reorder_autoloads to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
order | array | Yes | Ordered list of autoload names (first loads first) |
Parameters from the server's own tool schema.
Why reorder_autoloads is rated Medium
This tool modifies project state by changing the order in which autoload singletons are initialized in a Godot project. While reversible (order can be changed again), it affects runtime behavior and could cause subtle logic errors or cascade failures if dependencies between autoloads are not properly understood. It is Write category because changes are reversible, not Destructive.
From the tool's definition Tool name 'reorder_autoloads' and description 'Set the loading order of autoload singletons' indicates modification of project configuration—specifically reordering autoload execution order.
Attacks that exploit this kind of access
The rule that runs reorder_autoloads 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 reorder_autoloads, this is the rule to start with:
reorder_autoloads stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 reorder_autoloads call is checked against it from then on.
Questions about reorder_autoloads
Set the loading order of autoload singletons. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reorder_autoloads accepts 1 parameter: order. Required: order. 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 reorder_autoloads: 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.
reorder_autoloads is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reorder_autoloads 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 reorder_autoloads. 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.
reorder_autoloads 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