assert_game_state
Assert multiple game state conditions simultaneously
This record as markdown: /tools/keeveeg-godot-mcp/assert-game-state.md
What assert_game_state does on Godot
AI agents use assert_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 |
|---|---|---|---|
conditions | array | Yes | List of conditions that must all pass |
Parameters from the server's own tool schema.
Why assert_game_state is rated Medium
An AI agent can call assert_game_state faster than any human can review: one bad instruction and it creates or modifies resources in Godot by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (conditions[].path)
Attacks that exploit this kind of access
The rule that runs assert_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 assert_game_state, this is the rule to start with:
assert_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 assert_game_state call is checked against it from then on.
Questions about assert_game_state
Assert multiple game state conditions simultaneously. 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.
assert_game_state accepts 1 parameter: conditions. Required: conditions. 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 assert_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.
assert_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 assert_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 assert_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.
assert_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