This record as markdown: /tools/yanhuifair-godot-mcp/remove-autoload.md
What remove_autoload does on Godot
AI agents call remove_autoload to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name of the autoload to remove |
Parameters from the server's own tool schema.
Why remove_autoload is rated Critical
Autoloads in Godot are global singletons registered in project settings. Removing an autoload entry is an irreversible operation that deletes configuration state; dependent scripts and systems relying on that autoload will fail at runtime. This cannot be undone without manual reconfiguration, making it destructive rather than merely a reversible write.
From the tool's definition 'Remove an autoload entry' — autoloads are persistent configuration entries that initialize at game startup; removing one irreversibly deletes this registration and breaks dependent game logic.
Attacks that exploit this kind of access
The rule that runs remove_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 remove_autoload, this is the rule to start with:
remove_autoload is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every remove_autoload call is checked against it from then on.
Questions about remove_autoload
Remove an autoload entry. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_autoload accepts 1 parameter: name. Required: name. 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 remove_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.
remove_autoload is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue