This record as markdown: /tools/keeveeg-godot-mcp/select-nodes.md
What select_nodes does on Godot
AI agents invoke select_nodes 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 |
|---|---|---|---|
paths | array | Yes | List of node paths to select |
Parameters from the server's own tool schema.
Why select_nodes is rated High
Selecting nodes in a Godot editor triggers an editor UI action/operation that changes the editor's active selection state, which is an external operation affecting the editor environment. It's not a pure read (it changes state) but it's also not destructive or financial. It falls under Execute as it triggers an external editor operation.
From the tool's definition Select nodes in the editor
Attacks that exploit this kind of access
The rule that runs select_nodes 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 select_nodes, this is the rule to start with:
select_nodes 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 select_nodes call is checked against it from then on.
Questions about select_nodes
Select nodes in the 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.
select_nodes accepts 1 parameter: paths. Required: paths. 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 select_nodes: 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.
select_nodes 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 select_nodes 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 select_nodes. 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.
select_nodes is provided by the Godot MCP server (@keeveeg/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