This record as markdown: /tools/keeveeg-godot-mcp/save-editor-layout.md
What save_editor_layout does on Godot
AI agents use save_editor_layout 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 |
|---|---|---|---|
name | string | Yes | Layout name to save as |
Parameters from the server's own tool schema.
Why save_editor_layout is rated Medium
This tool creates or modifies editor layout configuration, which is reversible (layouts can be renamed, deleted, or overwritten). It does not retrieve data (Read), execute arbitrary code (Execute), permanently destroy data (Destructive), or involve money (Financial).
From the tool's definition The tool description states it will "Save the current editor layout under a name", which creates or modifies persistent editor configuration data.
Attacks that exploit this kind of access
The rule that runs save_editor_layout 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 save_editor_layout, this is the rule to start with:
save_editor_layout 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 save_editor_layout call is checked against it from then on.
Questions about save_editor_layout
Save the current editor layout under a name. 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.
save_editor_layout accepts 1 parameter: name. Required: name. 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 save_editor_layout: 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.
save_editor_layout 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 save_editor_layout 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 save_editor_layout. 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.
save_editor_layout is provided by the Godot MCP server (@keeveeg/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