This record as markdown: /tools/6ninelives-godot-mcp/save-scene.md
What save_scene does on Godot MCP
AI agents use save_scene to create or update resources in Godot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP environment.
Why save_scene is rated Medium
This tool writes/persists modifications to scene files, making it a Write action. However, severity is elevated to 'high' rather than 'medium' because in a game development context, saving scene files affects project state that other developers may depend on, and an AI agent misusing this (e.g., overwriting critical scenes with corrupted data) could significantly impact a development workflow and project integrity.
From the tool's definition The tool is named 'save_scene' with description 'Save changes to a scene file', which performs a write operation that modifies and persists data within a Godot project.
Attacks that exploit this kind of access
The rule that runs save_scene safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_scene, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot MCP, apply this rule, and every save_scene call is checked against it from then on.
Questions about save_scene
Save changes to a scene file. It is categorised as a Write tool in the Godot MCP 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 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 MCP. Nothing to install.
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 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 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.
save_scene is provided by the Godot MCP server (6ninelives/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