project_remove_autoload
Remove an autoload (ProjectSettings autoload/<name>). Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/project-remove-autoload.md
What project_remove_autoload does on Breakpoint
AI agents call project_remove_autoload to permanently remove resources in Breakpoint, 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 | Autoload / singleton name |
save | boolean | — | Persist to project.godot (default false) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why project_remove_autoload is rated Critical
The tool irreversibly deletes project configuration (autoload entries from ProjectSettings). While gated by confirmation, the underlying operation is destructive—once removed and persisted to project.godot, the autoload is gone. This is worse than Write (reversible modification) and qualifies as Destructive per the classification rules.
From the tool's definition Tool description explicitly states 'Remove an autoload' and marks it as 'DESTRUCTIVE'. It deletes a ProjectSettings autoload entry, which is a configuration resource that cannot be trivially restored without access to version control or backups.
Attacks that exploit this kind of access
The rule that runs project_remove_autoload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_remove_autoload, this is the rule to start with:
project_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 Breakpoint, apply this rule, and every project_remove_autoload call is checked against it from then on.
Questions about project_remove_autoload
Remove an autoload (ProjectSettings autoload/<name>). Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
project_remove_autoload accepts 3 parameters: name, save, confirm. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for project_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 Breakpoint. Nothing to install.
project_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 project_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 project_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.
project_remove_autoload is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue