Saves the specified scene (or active scene) to disk. Args: - scene_path (string, optional): res:// path of the scene to save. Omit for active scene. - save_as (string, optional): New res:// path to save a copy to (like Save As). Returns: Confirmation with the saved path.
AI agents use godot_save_scene to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
This tool creates or modifies scene files on disk, which is reversible (scenes can be edited or restored from version control). It does not delete or irreversibly destroy data, so it is Write rather than Destructive. The severity is high because an AI agent could overwrite critical scene files, corrupt game projects, or save malicious modifications to scenes that affect game logic.
From the tool's definition Tool description states 'Saves the specified scene (or active scene) to disk' with optional 'save_as' parameter for Save As functionality. This modifies files on disk by persisting scene data.
Attacks that exploit this kind of access
Saves the specified scene (or active scene) to disk. Args: - scene_path (string, optional): res:// path of the scene to save. Omit for active scene. - save_as (string, optional): New res:// path to save a copy to (like Save As). Returns: Confirmation with the saved path. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for godot_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 Server. Nothing to install.
godot_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 godot_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 godot_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.
godot_save_scene is provided by the Godot MCP Server MCP server (ricky-yosh/godot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →