editor_mark_scene_unsaved
Mark the current scene as having unsaved changes.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-mark-scene-unsaved.md
What editor_mark_scene_unsaved does on Godot
AI agents use editor_mark_scene_unsaved 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.
Why editor_mark_scene_unsaved is rated Medium
Reversibly changes scene save state metadata without destroying data or executing code.
From the tool's definition Mark scene unsaved changes; modifies editor state
Attacks that exploit this kind of access
The rule that runs editor_mark_scene_unsaved 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_mark_scene_unsaved, this is the rule to start with:
editor_mark_scene_unsaved 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_mark_scene_unsaved call is checked against it from then on.
Questions about editor_mark_scene_unsaved
Mark the current scene as having unsaved changes. 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.
Register the Godot MCP server in PolicyLayer and add a rule for editor_mark_scene_unsaved: 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_mark_scene_unsaved 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_mark_scene_unsaved 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_mark_scene_unsaved. 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_mark_scene_unsaved 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