editor_get_scene_changes
Check if current scene has unsaved changes.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-get-scene-changes.md
What editor_get_scene_changes does on Godot
AI agents call editor_get_scene_changes to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why editor_get_scene_changes is rated Low
This is a query operation that examines editor state to determine if changes exist. It retrieves information about the scene status without modifying, executing, or deleting anything. The low severity reflects that querying editor state poses minimal risk even if misused by an AI agent.
From the tool's definition The tool name 'editor_get_scene_changes' and description 'Check if current scene has unsaved changes' indicate a query operation that retrieves state information about the editor. The verb 'get' and 'check' denote read-only inspection with no modifications.
Attacks that exploit this kind of access
The rule that runs editor_get_scene_changes 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_get_scene_changes, this is the rule to start with:
editor_get_scene_changes is read-only, so it stays allowed. 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 editor_get_scene_changes call is checked against it from then on.
Questions about editor_get_scene_changes
Check if current scene has unsaved changes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for editor_get_scene_changes: 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.
editor_get_scene_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the editor_get_scene_changes 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 editor_get_scene_changes. 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.
editor_get_scene_changes 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue