editor_open_dock
Open a dock: filesystem, inspector, scene, output.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-open-dock.md
What editor_open_dock does on Godot
AI agents invoke editor_open_dock to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
dock | string | Yes | Dock name: filesystem, inspector, scene, output |
Parameters from the server's own tool schema.
Why editor_open_dock is rated High
Opening a dock is an editor UI operation that triggers an external effect (changing the Godot editor's visible panels/state). It doesn't read, write, or destroy data, but it does execute an action in an external application whose effect depends on the argument (which dock to open). Severity is low because misuse has minimal blast radius — it only affects editor UI state.
From the tool's definition "Open a dock: filesystem, inspector, scene, output" — triggers a UI action in the Godot editor, causing an external application state change
Attacks that exploit this kind of access
The rule that runs editor_open_dock 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_open_dock, this is the rule to start with:
editor_open_dock stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_open_dock call is checked against it from then on.
Questions about editor_open_dock
Open a dock: filesystem, inspector, scene, output. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
editor_open_dock accepts 1 parameter: dock. Required: dock. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for editor_open_dock: 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.
editor_open_dock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the editor_open_dock 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.
Set action: deny in the PolicyLayer policy for editor_open_dock. 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.
editor_open_dock 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.
More on Godot, and thousands of servers like it.
Across the catalogue