# editor_get_stack_trace Get current call stack from debugger. Agent View of the PolicyLayer registry record for `editor_get_stack_trace`. HTML page: https://policylayer.com/tools/yanhuifair-godot-mcp/editor-get-stack-trace ## Facts - Tool: `editor_get_stack_trace` - Server: Godot (`@yanhuifair/godot-mcp`) — https://policylayer.com/tools/yanhuifair-godot-mcp.md - Install: `npx -y @yanhuifair/godot-mcp` - Homepage: git+https://github.com/yanhuifair/Godot-MCP.git - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "editor_get_stack_trace", "arguments": {} } } ``` ## Why editor_get_stack_trace is rated Low This tool retrieves debugging information (call stack) from the Godot editor's debugger. It performs a read-only query of the current execution state without modifying, creating, deleting, or executing any code. The minimal blast radius and lack of side effects place it firmly in the Read category with low severity. From the tool's own definition: "Tool name 'editor_get_stack_trace' and description 'Get current call stack from debugger' indicate a retrieval operation. The verb 'get' and the passive nature of reading debugger state confirm this is a query with no side effects." ## Use case AI agents call editor_get_stack_trace 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. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Godot: ```json { "version": "1", "default": "deny", "tools": { "editor_get_stack_trace": {} } } ``` ## Other tools on Godot (281) - `delete_file` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/delete-file.md - `editor_delete_asset` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-delete-asset.md - `editor_delete_selected` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-delete-selected.md - `editor_remove_autoload` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-remove-autoload.md - `editor_remove_input_action` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-remove-input-action.md - `editor_remove_node` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-remove-node.md - `remove_animation_track` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-animation-track.md - `remove_audio_bus` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-audio-bus.md - `remove_autoload` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-autoload.md - `remove_input_action` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-input-action.md - `remove_node` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-node.md - `remove_shader_graph_node` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-shader-graph-node.md - `compile_shader` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/compile-shader.md - `editor_bake_lightmaps` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-bake-lightmaps.md - `editor_bake_navigation` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-bake-navigation.md - `editor_debug_break` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-break.md - `editor_debug_continue` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-continue.md - `editor_debug_step` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-step.md - `editor_debug_step_over` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-step-over.md - `editor_enable_plugin` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-enable-plugin.md - `editor_evaluate_expression` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-evaluate-expression.md - `editor_focus` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-focus.md - `editor_get_class_doc` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-get-class-doc.md - `editor_open_asset` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-open-asset.md - `editor_open_dock` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-open-dock.md - `editor_play` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-play.md - `editor_reimport_asset` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-reimport-asset.md - `editor_reload_scene` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-reload-scene.md - `editor_run_gdscript` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-run-gdscript.md - `editor_run_specific_scene` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-run-specific-scene.md - …and 251 more: https://policylayer.com/tools/yanhuifair-godot-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=yanhuifair-godot-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/yanhuifair-godot-mcp