compare_save_states
Compare two save states and return a diff of their contents
This record as markdown: /tools/keeveeg-godot-mcp/compare-save-states.md
What compare_save_states does on Godot
AI agents call compare_save_states 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
slot_a | integer | Yes | First save slot to compare (0-99) |
slot_b | integer | Yes | Second save slot to compare (0-99) |
Parameters from the server's own tool schema.
Why compare_save_states is rated Low
This tool reads and compares two save states, returning a diff. It retrieves and analyzes data without modifying, deleting, or executing anything. The operation is purely informational.
From the tool's definition Compare two save states and return a diff of their contents
Attacks that exploit this kind of access
The rule that runs compare_save_states 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 compare_save_states, this is the rule to start with:
compare_save_states 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 compare_save_states call is checked against it from then on.
Questions about compare_save_states
Compare two save states and return a diff of their contents. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
compare_save_states accepts 2 parameters: slot_a, slot_b. Required: slot_a, slot_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 compare_save_states: 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.
compare_save_states 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 compare_save_states 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 compare_save_states. 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.
compare_save_states is provided by the Godot MCP server (@keeveeg/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