editor_set_node_properties
Set multiple properties on a node at once.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-set-node-properties.md
What editor_set_node_properties does on Godot
AI agents use editor_set_node_properties to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path |
properties | object | Yes | Properties to set |
Parameters from the server's own tool schema.
Why editor_set_node_properties is rated Medium
This tool modifies node properties in a Godot scene, which is a Write operation (creates or modifies data reversibly). It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). However, severity is high because an AI agent could misconfigure critical game nodes (physics, rendering, logic) affecting game behavior, performance, or stability.
From the tool's definition Tool name 'editor_set_node_properties' and description 'Set multiple properties on a node at once' indicate modification of node state. The 'Set' verb and 'properties' mutation confirm reversible data modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_set_node_properties 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_node_properties, this is the rule to start with:
editor_set_node_properties stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_node_properties call is checked against it from then on.
Questions about editor_set_node_properties
Set multiple properties on a node at once. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
editor_set_node_properties accepts 2 parameters: path, properties. Required: path, properties. 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_node_properties: 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_node_properties is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the editor_set_node_properties 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_node_properties. 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_node_properties 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.
This server
Across the catalogue