This record as markdown: /tools/keeveeg-godot-mcp/load-game-state.md
What load_game_state does on Godot
AI agents call load_game_state 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 | integer | Yes | Save slot number to load (0-99) |
Parameters from the server's own tool schema.
Why load_game_state is rated Low
Loading game state is a read operation that retrieves data from storage without side effects. While loading a state may change the runtime environment of the game, the tool itself only reads/retrieves existing data and does not create, modify, delete, or execute arbitrary operations. The context of a Godot game engine MCP server confirms this is a standard save-load game feature with read semantics.
From the tool's definition Tool name 'load_game_state' with description 'Load a game state from a numbered save slot' indicates retrieval of previously saved game data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs load_game_state 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 load_game_state, this is the rule to start with:
load_game_state 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 load_game_state call is checked against it from then on.
Questions about load_game_state
Load a game state from a numbered save slot. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
load_game_state accepts 1 parameter: slot. Required: slot. 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 load_game_state: 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.
load_game_state 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 load_game_state 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 load_game_state. 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.
load_game_state 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