Run the project (or a specific scene) in the Godot game window.
AI agents invoke play_scene 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.
play_scene triggers execution of Godot project code or specific scenes within the game engine. While not destructive per se, executing arbitrary game code can have unpredictable side effects depending on what logic is embedded in the scene—including I/O operations, network calls, or modifications to game state.
From the tool's definition Tool description states "Run the project (or a specific scene) in the Godot game window." The verb "Run" combined with execution of game code/scenes qualifies as executing external operations whose effects depend on arguments (the scene chosen).
Attacks that exploit this kind of access
Run the project (or a specific scene) in the Godot game window. 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.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for play_scene: 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.
play_scene 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 play_scene 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 play_scene. 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.
play_scene 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.
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 →