editor_read_current_scene

Read live editor scene tree.

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-read-current-scene.md

WHAT IT DOES

What editor_read_current_scene does on Godot

AI agents call editor_read_current_scene 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_read_current_scene is rated Low

This tool retrieves the current scene structure from the Godot editor without modifying, executing, or deleting anything. It is a straightforward data retrieval operation analogous to inspecting project state. The blast radius of misuse is minimal — an agent could learn about scene structure but cannot cause harmful changes through this tool alone.

From the tool's definition Tool name contains 'read' and description states 'Read live editor scene tree' — a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

editor_read_current_scene Allowed

editor_read_current_scene 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_read_current_scene": {}
  }
}

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_read_current_scene call is checked against it from then on.

FAQ

Questions about editor_read_current_scene

What does the editor_read_current_scene tool do? +

Read live editor scene tree. 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_read_current_scene? +

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

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

Can I rate-limit editor_read_current_scene? +

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

Set action: deny in the PolicyLayer policy for editor_read_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_read_current_scene? +

editor_read_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 282 Godot tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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