Add multiple nodes to the scene in a single call.
AI agents use batch_add_nodes 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.
This tool creates/modifies the game scene by adding nodes, which is reversible (nodes can be deleted). It does not execute arbitrary code, delete data irreversibly, or move money. The 'batch' aspect increases the Write severity slightly (medium vs.
From the tool's definition Tool is named 'batch_add_nodes' and described as 'Add multiple nodes to the scene in a single call.' The verb 'Add' combined with sibling tools like 'add_node', 'add_animation_track', 'add_audio_bus' all performing creation operations indicates this creates…
Attacks that exploit this kind of access
Add multiple nodes to the scene in a single call. 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 batch_add_nodes: 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.
batch_add_nodes 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 batch_add_nodes 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 batch_add_nodes. 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.
batch_add_nodes is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). 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 →