This record as markdown: /tools/keeveeg-godot-mcp/add-node.md
What add_node does on Godot
AI agents use add_node 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 |
|---|---|---|---|
name | string | Yes | Name for the new node |
type | string | Yes | Node type name (e.g. 'Sprite2D', 'CharacterBody3D') |
properties | object | — | Optional property key-value pairs |
parent_path | string | Yes | Parent node path (e.g. 'Player' or '' for root) |
Parameters from the server's own tool schema.
Why add_node is rated Medium
This tool creates or modifies scene data in Godot by introducing a new node. While this is a modification operation (Write category), it is reversible (nodes can be deleted or removed), so it does not rise to Destructive. The blast radius is medium because an agent could spam nodes or add problematic nodes, degrading performance or creating inconsistent scenes, but the impact is containable and undoable.
From the tool's definition Tool description states 'Add a new node to the scene tree' — this creates a new scene element, which is a reversible modification to the game/scene structure.
Attacks that exploit this kind of access
The rule that runs add_node 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 add_node, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every add_node call is checked against it from then on.
Questions about add_node
Add a new node to the scene tree. 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.
add_node accepts 4 parameters: name, type, properties, parent_path. Required: name, type, parent_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 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. Nothing to install.
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 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 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.
add_node 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.
This server
Across the catalogue