editor_play_current_scene

Play the currently edited scene from the editor.

SERVERGodot SOURCE@yanhuifair/godot-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-play-current-scene.md

WHAT IT DOES

What editor_play_current_scene does on Godot

AI agents invoke editor_play_current_scene 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.

RISK

Why editor_play_current_scene is rated High

Triggers external execution of a Godot scene within the editor environment.

From the tool's definition Play the currently edited scene from the editor

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs editor_play_current_scene 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 editor_play_current_scene, this is the rule to start with:

editor_play_current_scene Rate-limited

editor_play_current_scene 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": {
    "editor_play_current_scene": {
      "limits": [
        {
          "counter": "editor_play_current_scene_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_play_current_scene call is checked against it from then on.

FAQ

Questions about editor_play_current_scene

What does the editor_play_current_scene tool do? +

Play the currently edited scene from the editor. 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.

How do I enforce a policy on editor_play_current_scene? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_play_current_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. Nothing to install.

What risk level is editor_play_current_scene? +

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

Can I rate-limit editor_play_current_scene? +

Yes. Add a rate_limit block to the editor_play_current_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.

How do I block editor_play_current_scene completely? +

Set action: deny in the PolicyLayer policy for editor_play_current_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.

What MCP server provides editor_play_current_scene? +

editor_play_current_scene is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 386 Godot tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →music_play on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →