# save_scene

Save changes to a scene file

Agent View of the PolicyLayer registry record for `save_scene`. HTML page: https://policylayer.com/tools/6ninelives-godot-mcp/save-scene

## Facts

- Tool: `save_scene`
- Server: Godot MCP (`6ninelives/godot-mcp`) — https://policylayer.com/tools/6ninelives-godot-mcp.md
- Homepage: https://github.com/6NineLives/godot-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "save_scene",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Godot MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_scene": {
      "limits": [
        {
          "counter": "save_scene_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Godot MCP (17)

- `remove_node` — Destructive — https://policylayer.com/tools/6ninelives-godot-mcp/remove-node.md
- `launch_editor` — Execute — https://policylayer.com/tools/6ninelives-godot-mcp/launch-editor.md
- `run_project` — Execute — https://policylayer.com/tools/6ninelives-godot-mcp/run-project.md
- `stop_project` — Execute — https://policylayer.com/tools/6ninelives-godot-mcp/stop-project.md
- `get_debug_output` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/get-debug-output.md
- `get_documentation_file` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/get-documentation-file.md
- `get_documentation_tree` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/get-documentation-tree.md
- `get_godot_version` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/get-godot-version.md
- `get_project_info` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/get-project-info.md
- `get_uid` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/get-uid.md
- `list_projects` — Read — https://policylayer.com/tools/6ninelives-godot-mcp/list-projects.md
- `add_node` — Write — https://policylayer.com/tools/6ninelives-godot-mcp/add-node.md
- `create_scene` — Write — https://policylayer.com/tools/6ninelives-godot-mcp/create-scene.md
- `edit_node` — Write — https://policylayer.com/tools/6ninelives-godot-mcp/edit-node.md
- `export_mesh_library` — Write — https://policylayer.com/tools/6ninelives-godot-mcp/export-mesh-library.md
- `load_sprite` — Write — https://policylayer.com/tools/6ninelives-godot-mcp/load-sprite.md
- `update_project_uids` — Write — https://policylayer.com/tools/6ninelives-godot-mcp/update-project-uids.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=6ninelives-godot-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/6ninelives-godot-mcp