editor_save

Save current scene in editor.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-save.md

WHAT IT DOES

What editor_save does on Godot

AI agents use editor_save 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.

RISK

Why editor_save is rated Medium

The tool creates or modifies data by saving the current scene, which is a reversible write operation. Severity is medium because saving a scene can overwrite existing work (loss of prior state), but the action is reversible through undo/version control and does not destroy data permanently or execute arbitrary code.

From the tool's definition Tool name 'editor_save' and description 'Save current scene in editor' indicate the tool modifies and persists data (the scene state) to storage.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs editor_save 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, this is the rule to start with:

editor_save Rate-limited

editor_save 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_save": {
      "limits": [
        {
          "counter": "editor_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_save call is checked against it from then on.

FAQ

Questions about editor_save

What does the editor_save tool do? +

Save current scene in editor. 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.

How do I enforce a policy on editor_save? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_save: 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.

What risk level is editor_save? +

editor_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit editor_save? +

Yes. Add a rate_limit block to the editor_save 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.

How do I block editor_save completely? +

Set action: deny in the PolicyLayer policy for editor_save. 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.

What MCP server provides editor_save? +

editor_save 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →