execute_game_script · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_game_script does on Godot MCP Server

AI agents invoke execute_game_script to trigger actions in Godot MCP Server. 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.

WHY IT NEEDS A POLICY

Why execute_game_script needs a policy

This tool permits execution of arbitrary GDScript code within the active Godot game runtime. While not destructive per se (code execution alone doesn't necessarily delete data), it represents the Execute category because: (1) it triggers external operations (game script execution), (2) the effects depend entirely on the arguments provided (arbitrary code), and (3) an AI agent could misuse it to modify game state,…

From the tool's definition Tool description states 'Execute arbitrary GDScript code in the running game context.' The word 'arbitrary' combined with 'Execute' and 'code' clearly indicates dynamic code execution with unpredictable side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_game_script Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_game_script": {
      "limits": [
        {
          "counter": "execute_game_script_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_game_script

What does the execute_game_script tool do? +

Execute arbitrary GDScript code in the running game context. It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_game_script? +

Register the Godot MCP Server 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 MCP Server. Nothing to install.

What risk level is execute_game_script? +

execute_game_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_game_script? +

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.

How do I block execute_game_script completely? +

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.

What MCP server provides execute_game_script? +

execute_game_script is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.