editor_open_dock · Godot MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required	Description
`dock`	string	Yes	Dock name: filesystem, inspector, scene, output

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_open_dock needs a policy

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

Recommended rule Ready

Verdict

editor_open_dock Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_open_dock": {
      "limits": [
        {
          "counter": "editor_open_dock_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about editor_open_dock

What does the editor_open_dock tool do? +

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.

What parameters does editor_open_dock accept? +

editor_open_dock accepts 1 parameter: dock. Required: dock. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_open_dock? +

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.

What risk level is editor_open_dock? +

editor_open_dock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit editor_open_dock? +

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.

How do I block editor_open_dock completely? +

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.

What MCP server provides editor_open_dock? +

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.