autoload_remove

Remove an autoload singleton from the project.

SERVERGodot SOURCEchanceflow/godot-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chanceflow-godot-mcp/autoload-remove.md

WHAT IT DOES

What autoload_remove does on Godot

AI agents call autoload_remove 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.

RISK

Why autoload_remove is rated Critical

Removing an autoload singleton is an irreversible deletion of a project-level configuration. Autoloads are globally accessible singletons; removing one can break project functionality across all scenes and scripts that depend on it, and this action cannot be easily undone without manual re-configuration.

From the tool's definition Remove an autoload singleton from the project

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs autoload_remove 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 autoload_remove, this is the rule to start with:

autoload_remove Hidden

autoload_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "autoload_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every autoload_remove call is checked against it from then on.

FAQ

Questions about autoload_remove

What does the autoload_remove tool do? +

Remove an autoload singleton from the project. 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.

How do I enforce a policy on autoload_remove? +

Register the Godot MCP server in PolicyLayer and add a rule for autoload_remove: 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.

What risk level is autoload_remove? +

autoload_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit autoload_remove? +

Yes. Add a rate_limit block to the autoload_remove 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.

How do I block autoload_remove completely? +

Set action: deny in the PolicyLayer policy for autoload_remove. 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.

What MCP server provides autoload_remove? +

autoload_remove is provided by the Godot MCP server (chanceflow/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 84 Godot tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →