editor_focus

Bring the Godot editor window to the foreground.

SERVERGodot SOURCE@yanhuifair/godot-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-focus.md

WHAT IT DOES

What editor_focus does on Godot

AI agents invoke editor_focus 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.

RISK

Why editor_focus is rated High

This tool triggers an external operation on the desktop environment — raising a window to the foreground — which is a side-effecting action rather than a pure read. It doesn't modify data, but it does interact with the OS windowing system. Severity is low because the blast radius is minimal (it only changes window focus).

From the tool's definition Bring the Godot editor window to the foreground

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs editor_focus 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_focus, this is the rule to start with:

editor_focus Rate-limited

editor_focus 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_focus": {
      "limits": [
        {
          "counter": "editor_focus_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_focus call is checked against it from then on.

FAQ

Questions about editor_focus

What does the editor_focus tool do? +

Bring the Godot editor window to the foreground. 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.

How do I enforce a policy on editor_focus? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_focus: 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_focus? +

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

Can I rate-limit editor_focus? +

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

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

editor_focus 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools → High-risk tools on this server →

Across the catalogue

focus_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →