editor_is_playing

Return whether the editor is currently playing a scene and which scene.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-is-playing.md

WHAT IT DOES

What editor_is_playing does on Godot

AI agents call editor_is_playing to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why editor_is_playing is rated Low

Queries editor state without side effects; information-only retrieval of active scene status.

From the tool's definition Return whether the editor is currently playing a scene.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

editor_is_playing Allowed

editor_is_playing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_is_playing": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about editor_is_playing

What does the editor_is_playing tool do? +

Return whether the editor is currently playing a scene and which scene. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_is_playing? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_is_playing: 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_is_playing? +

editor_is_playing is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit editor_is_playing? +

Yes. Add a rate_limit block to the editor_is_playing 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_is_playing completely? +

Set action: deny in the PolicyLayer policy for editor_is_playing. 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_is_playing? +

editor_is_playing 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 →

Across the catalogue

editor_context on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →