AI agents call diff_scene to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path_a | string | Yes | First scene path |
path_b | string | Yes | Second scene path |
ignore_whitespace | object | — | Ignore whitespace-only changes |
Parameters from the server's own tool schema.
This tool performs a comparison between two scene files, which is fundamentally a read operation. Diffing/comparing files retrieves their content and presents differences without creating, modifying, deleting, or executing any code. No side effects are produced by comparing data.
From the tool's definition Tool name 'diff_scene' and description 'Compare two scene files' indicate a read-only comparison operation that retrieves and analyzes data without modifying or executing anything.
Attacks that exploit this kind of access
Compare two scene files. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
diff_scene accepts 3 parameters: path_a, path_b, ignore_whitespace. Required: path_a, path_b. 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 diff_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. Nothing to install.
diff_scene 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 diff_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 diff_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.
diff_scene 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.
diff_scene is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →