execute_game_script
🔴 Game must be running. Execute a GDScript snippet in the running game context
This record as markdown: /tools/keeveeg-godot-mcp/execute-game-script.md
What execute_game_script does on Godot
AI agents invoke execute_game_script to trigger actions in Godot. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | GDScript code to execute |
Parameters from the server's own tool schema.
Why execute_game_script is rated High
This tool runs arbitrary GDScript code in an active game environment. An AI agent could misuse it to crash the game, corrupt game state, access sensitive data, trigger unintended actions, or compromise the game's integrity. The effects are entirely dependent on the script passed as input, making this a high-risk execution endpoint warranting 'critical' severity.
From the tool's definition Tool name 'execute_game_script' combined with description 'Execute a GDScript snippet in the running game context' directly indicates arbitrary code execution.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs execute_game_script 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 execute_game_script, this is the rule to start with:
execute_game_script stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 execute_game_script call is checked against it from then on.
Questions about execute_game_script
🔴 Game must be running. Execute a GDScript snippet in the running game context. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
execute_game_script accepts 1 parameter: code. Required: code. 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 execute_game_script: 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.
execute_game_script 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 execute_game_script 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 execute_game_script. 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.
execute_game_script 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.
Across the catalogue