save_game_state
Save the current game state to a numbered slot with optional metadata
This record as markdown: /tools/keeveeg-godot-mcp/save-game-state.md
What save_game_state does on Godot
AI agents use save_game_state to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
slot | integer | Yes | Save slot number (0-99) |
metadata | object | — | Optional metadata to store with the save (e.g. player name, level, timestamp) |
Parameters from the server's own tool schema.
Why save_game_state is rated Medium
This tool persists game state data to storage (a numbered slot), which is a write operation. It is reversible—saved states can be overwritten or deleted. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'save_game_state' and description 'Save the current game state to a numbered slot with optional metadata' indicates creation and storage of data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs save_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 save_game_state, this is the rule to start with:
save_game_state stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 save_game_state call is checked against it from then on.
Questions about save_game_state
Save the current game state to a numbered slot with optional metadata. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
save_game_state accepts 2 parameters: slot, metadata. 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 save_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.
save_game_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_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 save_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.
save_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