Save the currently open editor scene through the live editor bridge
AI agents use editor_save_scene to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool writes scene data to persistent storage. While the operation is reversible (not destructive like delete/drop), it irreversibly overwrites the current scene state. The impact on a Godot project is significant—a careless or malicious save could corrupt game logic or asset configurations.
From the tool's definition Tool name 'editor_save_scene' and description 'Save the currently open editor scene through the live editor bridge' indicate a write operation that modifies the scene file on disk.
Documented attack patterns abuse exactly the kind of access editor_save_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_save_scene:
{
"version": "1",
"default": "deny",
"tools": {
"editor_save_scene": {
"limits": [
{
"counter": "editor_save_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}editor_save_scene 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.
Free to start. No card required.
Save the currently open editor scene through the live editor bridge. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for editor_save_scene: 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 Devtool. Nothing to install.
editor_save_scene 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 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. 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 is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.