This record as markdown: /tools/yanhuifair-godot-mcp/editor-set-selection.md
What editor_set_selection does on Godot
AI agents invoke editor_set_selection 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 |
|---|---|---|---|
value | object | — | Property value |
property | object | — | Property key to set |
node_path | string | Yes | Node path to select |
Parameters from the server's own tool schema.
Why editor_set_selection is rated High
This tool triggers an action in the Godot editor (selecting a node), which constitutes an external operation/UI interaction rather than a pure data read. However, it has minimal blast radius as it only changes the editor's selection state without modifying any data or executing code.
From the tool's definition Select node in editor
Attacks that exploit this kind of access
The rule that runs editor_set_selection 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_set_selection, this is the rule to start with:
editor_set_selection 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_set_selection call is checked against it from then on.
Questions about editor_set_selection
Select node in editor. 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_set_selection accepts 3 parameters: value, property, node_path. Required: node_path. 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_set_selection: 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_set_selection 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_set_selection 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_set_selection. 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_set_selection 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