Add a node to the currently open editor scene through UndoRedo without externally rewriting the scene file
AI agents use editor_add_node to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This is a Write operation because it creates/modifies scene data (adding a node) in a reversible manner via the UndoRedo system. It does not execute arbitrary code (Execute), delete data irreversibly (Destructive), or move money (Financial).
From the tool's definition Tool description states it will 'Add a node to the currently open editor scene' and uses 'UndoRedo' mechanism, indicating reversible data modification of an open scene.
Documented attack patterns abuse exactly the kind of access editor_add_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_add_node:
{
"version": "1",
"default": "deny",
"tools": {
"editor_add_node": {
"limits": [
{
"counter": "editor_add_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}editor_add_node 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.
Free to start. No card required.
Add a node to the currently open editor scene through UndoRedo without externally rewriting the scene file. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for editor_add_node: 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 Devtool. Nothing to install.
editor_add_node 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_add_node 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_add_node. 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_add_node is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.