editor_add_autoload
Add an autoload singleton via editor API.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-add-autoload.md
What editor_add_autoload does on Godot
AI agents use editor_add_autoload 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 |
|---|---|---|---|
name | string | Yes | |
path | string | Yes |
Parameters from the server's own tool schema.
Why editor_add_autoload is rated Medium
Autoloads are persistent global singletons that load at startup and persist across scenes. Adding an autoload modifies the project's autoload registry (typically persisted in project.godot), affecting how the game initializes. This is reversible (can be removed), but altering autoloads can change application behavior significantly, potentially loading malicious singletons.
From the tool's definition Tool name 'editor_add_autoload' and description 'Add an autoload singleton via editor API' indicate creation/modification of autoload configuration in Godot.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_add_autoload 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_add_autoload, this is the rule to start with:
editor_add_autoload 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 editor_add_autoload call is checked against it from then on.
Questions about editor_add_autoload
Add an autoload singleton via editor API. 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.
editor_add_autoload accepts 2 parameters: name, path. Required: name, 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 editor_add_autoload: 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_add_autoload 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 editor_add_autoload 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_add_autoload. 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_add_autoload 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