This record as markdown: /tools/keeveeg-godot-mcp/add-autoload-config.md
What add_autoload_config does on Godot
AI agents use add_autoload_config 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 | Autoload singleton name |
path | string | Yes | Script or scene path (e.g. 'res://autoload/global.gd') |
enabled | boolean | — | Whether the autoload is enabled (default: true) |
Parameters from the server's own tool schema.
Why add_autoload_config is rated Medium
This tool creates or modifies project autoload configuration, which is a reversible write operation. It adds a singleton to the Godot project's configuration rather than executing arbitrary code or destructively removing data. The medium severity reflects that misconfigured autoloads could cause unintended behavior or resource consumption, but changes can be undone through project editing.
From the tool's definition Tool name 'add_autoload_config' and description 'Add an autoload singleton to the project' indicate modification of project configuration.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs add_autoload_config 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 add_autoload_config, this is the rule to start with:
add_autoload_config 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 add_autoload_config call is checked against it from then on.
Questions about add_autoload_config
Add an autoload singleton to the project. 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.
add_autoload_config accepts 3 parameters: name, path, enabled. 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 add_autoload_config: 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.
add_autoload_config 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 add_autoload_config 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 add_autoload_config. 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.
add_autoload_config 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