AI agents use add_node to create or update resources in Godot MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP environment.
This tool creates new nodes within scenes, which modifies project state reversibly. While it changes the scene structure, it does not execute arbitrary code, delete data, or cause financial impact. The medium severity reflects that an AI agent could add many unwanted nodes or interfere with game logic, but changes can be undone via Godot's undo system or by not saving the project.
From the tool's definition Tool name 'add_node' and description 'Add a node to an existing scene' indicate creation/modification of scene structure within a Godot project.
Documented attack patterns abuse exactly the kind of access add_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_node:
{
"version": "1",
"default": "deny",
"tools": {
"add_node": {
"limits": [
{
"counter": "add_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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 an existing scene. It is categorised as a Write tool in the Godot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 MCP. 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 (leesinliang/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Godot MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Godot MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.