editor_save_scene_as
Save the current scene under a new res:// path (optionally with preview).
This record as markdown: /tools/yanhuifair-godot-mcp/editor-save-scene-as.md
What editor_save_scene_as does on Godot
AI agents use editor_save_scene_as 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 |
|---|---|---|---|
path | string | Yes | Destination scene path, must start with res:// (e.g. res://levels/level2.tscn) |
with_preview | object | — | Generate a thumbnail preview for the FileSystem dock |
Parameters from the server's own tool schema.
Why editor_save_scene_as is rated Medium
Creates or modifies scene files in the project; reversible but impacts project state significantly.
From the tool's definition Save scene under new res:// path; creates/modifies project files.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_save_scene_as 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 editor_save_scene_as, this is the rule to start with:
editor_save_scene_as 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 editor_save_scene_as call is checked against it from then on.
Questions about editor_save_scene_as
Save the current scene under a new res:// path (optionally with preview). 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.
editor_save_scene_as accepts 2 parameters: path, with_preview. Required: 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 editor_save_scene_as: 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.
editor_save_scene_as 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 editor_save_scene_as 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 editor_save_scene_as. 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.
editor_save_scene_as 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.
This server
Across the catalogue