add_node
AI agents use add_node to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
Adding a node to a Godot scene creates or modifies data reversibly—nodes can be deleted and scenes can be reverted. This is a Write operation rather than Execute because it manipulates scene structure via a defined API action rather than running arbitrary code. Severity is medium because misuse could corrupt a game project's structure, but the effect is reversible and scoped to scene nodes.
From the tool's definition Tool name is 'add_node' in a Godot game engine context; sibling tools include 'create_scene', 'get_scene_tree', and 'run_project', indicating this modifies scene structure. Description is empty, preventing direct confirmation.
Attacks that exploit this kind of access
add_node. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server 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 MCP Server. 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 MCP server (matula/godot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →