editor_get_state

Return the currently edited scene, its root type/path, and the current node selection.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-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/godot-breakpoint-mcp/editor-get-state.md

What editor_get_state does on Godot Breakpoint

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

Why editor_get_state is rated Low

This tool queries and retrieves internal editor state (scene information, node types, paths, and selections) without creating, modifying, deleting, or executing anything. It is a straightforward read operation with minimal security risk—an agent could learn about the current editing context, but cannot modify or harm anything through this information alone.

From the tool's definition Tool name and description indicate 'Return the currently edited scene, its root type/path, and the current node selection'—purely retrieving state information with no modifications, side effects, or external operations.

Risk signalsAdmin/system-level operation

Questions about editor_get_state

What does the editor_get_state tool do? +

Return the currently edited scene, its root type/path, and the current node selection. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_get_state? +

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

What risk level is editor_get_state? +

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

Can I rate-limit editor_get_state? +

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

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

editor_get_state is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Godot Breakpoint, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Godot Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.