project_add_autoload
Register an autoload (ProjectSettings autoload/<name>) pointing at a res:// script or scene, enabled as a global singleton by default. Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/project-add-autoload.md
What project_add_autoload does on Breakpoint
AI agents use project_add_autoload to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Autoload / singleton name |
path | string | Yes | res:// path to a .gd script or .tscn scene |
save | boolean | — | Persist to project.godot (default false) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
enabled | boolean | — | Enable as a global singleton (default true) |
Parameters from the server's own tool schema.
Why project_add_autoload is rated Medium
This tool modifies project settings by registering a new autoload entry, which is a write operation. While it can persist changes to project.godot (potentially hard to undo), it does not delete or overwrite existing data — it adds a new configuration entry.
From the tool's definition Register an autoload (ProjectSettings autoload/<name>) pointing at a res:// script or scene, enabled as a global singleton by default. Set save=true to persist to project.godot.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs project_add_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_add_autoload, this is the rule to start with:
project_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 Breakpoint, apply this rule, and every project_add_autoload call is checked against it from then on.
Questions about project_add_autoload
Register an autoload (ProjectSettings autoload/<name>) pointing at a res:// script or scene, enabled as a global singleton by default. Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
project_add_autoload accepts 5 parameters: name, path, save, confirm, enabled. Required: name, path. 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_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 Breakpoint. Nothing to install.
project_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 project_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 project_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.
project_add_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.
This server
Across the catalogue