// SCAN REPORT

Godot Devtool

101 tools. 62 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

62 can modify or destroy data

39 read-only

101 tools total

Community server · catalogue entry verified 11/06/2026

How to control Godot Devtool ↓

TOOL MAP

Read (39) Write / Execute (57) Destructive / Financial (5)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High delete_node This tool permanently removes scene graph nodes, destroying their configuration, child hierarchy, and associated data within the scene file. Destructive · High editor_delete_node This tool permanently removes nodes from a Godot scene structure. Destructive · Low clear_debug_output Clearing buffered output is a one-way operation that permanently discards accumulated debug/log data. Destructive · High filesystem_delete This tool permanently removes files or directories from the Godot project filesystem.

62 of Godot Devtool's 101 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL GODOT DEVTOOL

PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_debug_output": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "animation": {
    "limits": [
      {
        "counter": "animation_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "resource_dependency_graph": {
    "limits": [
      {
        "counter": "resource_dependency_graph_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Godot Devtool — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GODOT DEVTOOL →

Free to start. No card required.

ALL 101 GODOT DEVTOOL TOOLS

DESTRUCTIVE 5 tools

Destructive clear_debug_output Clear buffered output for the currently running Godot project Destructive delete_node Delete a non-root node from a Godot scene Destructive editor_delete_node Delete a non-root node from the currently open editor scene through UndoRedo Destructive filesystem_delete Delete a project-local file or directory with explicit confirmation Destructive filesystem_preview_delete Preview a project-local delete operation without deleting files

EXECUTE 15 tools

Execute browser_visualizer_start Start a local read-only browser dashboard for Godot editor/runtime bridge status and live-route guidance Execute browser_visualizer_stop Stop the local Browser visualizer HTTP dashboard Execute launch_editor Reuse an already connected Godot editor for a project, launch one only when no bridge is connected, and refuse Execute run_project Run the Godot project and capture output Execute run_project_checks Run stable project checks for CI, review, and release workflows Execute stop_project Stop the currently running Godot project Execute stop_run_instance Stop one Godot run instance by runId Execute check_gdscript_syntax Run Godot --check-only against a GDScript file and return diagnostics Execute broker_cleanup_idle Stop the transient shared broker listener only when no clients, runs, or pending commands require it Execute editor_select_node Select a node in the live Godot editor when an editor bridge is available Execute editor_undo_redo Perform undo or redo in the live Godot editor when an editor bridge is available Execute export_project Run a controlled Godot export for a configured preset Execute plugin_cleanup_port Explicitly inspect and optionally stop stale godot-devtool WebSocket bridge listeners on a local port Execute plugin_reload Reload the godot-devtool editor plugin through the WebSocket bridge

WRITE 42 tools

Write animation Create, inspect, remove, and edit AnimationPlayer tracks and keyframes Write group List, add, or remove node groups Write load_sprite Load a sprite into a Sprite2D node Write add_node Add a node to an existing scene Write animation_state_machine Create, inspect, and configure AnimationTree state machines Write audio Create and list AudioStreamPlayer nodes with basic playback configuration Write create_gameplay_prototype Create a high-level block-based gameplay prototype scaffold in a Godot project Write create_scene Create a new Godot scene file Write create_workflow_test_scene Create a small Godot scene for validating MCP scene/script/check workflows Write editor_add_node Add a node to the currently open editor scene through UndoRedo without externally rewriting the scene file Write editor_duplicate_node Duplicate a node in the currently open editor scene through UndoRedo Write editor_inspector_set_properties Write Inspector properties on the selected or addressed node through the live editor bridge Write editor_move_node Move or reparent a node in the currently open editor scene through UndoRedo Write editor_rename_node Rename a node in the currently open editor scene through UndoRedo Write editor_save_scene Save the currently open editor scene through the live editor bridge Write export_mesh_library Export a scene as a MeshLibrary resource Write filesystem_write Write a UTF-8 text file inside a Godot project Write generate_ci_snippet Generate GitHub Actions or GitLab CI snippets for Godot headless checks, export preflight, release export, and Write geometry Create and list basic 2D geometry/debug drawing nodes Write lighting Create and list basic Godot light and environment nodes Write material Create, read, update, and apply Godot material resources Write node_duplicate Duplicate a node in a Godot scene Write node_move Move a node by setting its position or reparenting it in a Godot scene Write particle Create and list basic Godot particle emitter nodes Write physics Create, inspect, configure, template, and analyze physics bodies, areas, collision layers, and shapes Write plugin_install Install the godot-devtool WebSocket editor/runtime plugin into a Godot project Write project_input_action List or update project InputMap actions in project.godot Write project_set_setting Update Godot project.godot settings with dry-run preview and audit logging Write rename_node Rename a node in a Godot scene Write resource_create Create a simple structured Godot resource file Write resource_save Save text-based Godot resource content with overwrite protection Write save_scene Save changes to a scene file Write script_attach Attach a GDScript resource to a node in a scene Write script_create Create a GDScript file inside a Godot project Write script_write Write full GDScript content with overwrite protection Write set_safety_policy Configure project write allowlists and blocked paths in .godot-devtool/safety.json Write shader Create, read, inspect, and configure ShaderMaterial parameters Write tilemap Create, list, and edit TileMapLayer or legacy TileMap nodes Write ui Create Control nodes, reusable UI templates, themes, and automatic signal wiring Write update_export_preset Update fields or options for a configured Godot export preset Write update_node_properties Update properties on a node in a Godot scene Write update_project_uids Update UID references in a Godot project by resaving resources (for Godot 4.4+)

READ 39 tools

Read resource_dependency_graph Build a resource dependency graph and identify orphan resources Read analyze_script_references Analyze a GDScript file for class, functions, exports, node paths, and resource references Read broker_status Read the shared godot-devtool 3.0 WebSocket broker status, connected clients, pending commands, and leases Read browser_visualizer_status Read the local Browser visualizer URL, project filter, and connected editor/runtime bridge clients Read check_export_presets Inspect Godot export presets and report pre-export issues Read editor_get_selection Return the current editor selection when a live editor bridge is available Read editor_inspector_get_properties Read Inspector properties from the selected or addressed node through the live editor bridge Read filesystem_list List files and directories inside a Godot project Read filesystem_read Read a UTF-8 text file inside a Godot project Read get_audit_log Read godot-devtool project audit log entries Read get_audit_replay Summarize godot-devtool audit log entries into replay steps, counters, and risk highlights Read get_capabilities Return a lightweight godot-devtool tool catalog by default, with optional filtered input schemas by route grou Read get_debug_output Get the current debug output and errors Read get_export_presets Read configured Godot export presets Read get_godot_version Get the installed Godot version Read get_node_properties Read selected properties from a node in a Godot scene Read get_project_info Retrieve metadata about a Godot project Read get_resource_index Return a categorized resource index for a Godot project Read get_rollback_suggestions Return honest rollback guidance for an operation, audit entry, or changed paths Read get_safety_policy Read the project-local godot-devtool safety policy and default enforcement state Read get_scene_tree Return the node tree for a Godot scene Read get_script_index Return GDScript files with class, base class, exported variables, and functions Read get_uid Get the UID for a specific file in a Godot project (for Godot 4.4+) Read list_bridge_sessions List connected editor/runtime bridge sessions with sessionId, runId, project path, context, and last-seen time Read list_projects List Godot projects in a directory Read list_run_instances List Godot game/editor run instances managed by this MCP server Read node_find Find nodes in a scene by name, type, or path substring Read node_get Get node information from a Godot scene Read plugin_dock_status Return machine-readable godot-devtool Dock labels, tooltips, status dots, buttons, visibility, and bridge diag Read plugin_status Read godot-devtool plugin installation status, WebSocket bridge configuration, connected clients, and occupied Read project_get_settings Read Godot project.godot settings by section or section/key list Read read_script_file Read a GDScript file from a Godot project Read resource_load Load a text-based Godot resource from the project Read scene_get_current Return the current scene tracked by this MCP session, if one was opened Read signal List, connect, or disconnect node signals in a scene Read export_matrix Summarize export targets, platform families, signing/template status, and CI steps Read preview_write_safety Preview safety policy and diff summary metadata for proposed writes or deletes Read resolve_bridge_target Resolve the editor/runtime bridge target for a project and report ambiguity candidates without sending a comma Read scene_open Open a scene in the MCP session using headless/file-based scene access

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent delete data through the Godot Devtool MCP server? +

Yes. The Godot Devtool server exposes 5 destructive tools including clear_debug_output, delete_node, editor_delete_node. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Godot Devtool? +

The Godot Devtool server has 42 write tools including animation, group, load_sprite. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Godot Devtool.

How many tools does the Godot Devtool MCP server expose? +

101 tools across 4 categories: Destructive, Execute, Read, Write. 39 are read-only. 62 can modify, create, or delete data.

How do I enforce a policy on Godot Devtool? +

Register the Godot Devtool MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Godot Devtool tool call.

Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GODOT DEVTOOL →

Free to start. No card required.

101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Godot Devtool

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL GODOT DEVTOOL

// ALL 101 GODOT DEVTOOL TOOLS

// RELATED SERVERS

// FAQ