Launch the Godot game with optional scene override
AI agents invoke run_game to trigger actions in Godot Sentinel MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers execution of game code with external side effects (rendering, input handling, game state changes, potential file I/O, network calls defined in the game). While not destructive on its own, the blast radius includes unintended game state modifications, resource consumption, or triggering of game-defined side effects.
From the tool's definition Tool launches the Godot game runtime ('Launch the Godot game'), which executes arbitrary game code and external operations whose effects depend on runtime arguments (scene override parameter).
Attacks that exploit this kind of access
Launch the Godot game with optional scene override. It is categorised as a Execute tool in the Godot Sentinel MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Sentinel MCP server in PolicyLayer and add a rule for run_game: 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 Sentinel MCP. Nothing to install.
run_game is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_game 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 run_game. 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.
run_game is provided by the Godot Sentinel MCP server (snack-jpg/godot-sentinel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →