add_mesh_instance
Add a MeshInstance3D with a primitive mesh type
This record as markdown: /tools/keeveeg-godot-mcp/add-mesh-instance.md
What add_mesh_instance does on Godot
AI agents use add_mesh_instance 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 |
|---|---|---|---|
parent | string | Yes | Parent node path. Use '' (empty string) to add at scene root, or a node name/path (e.g. 'Player' or 'Player/Sprites') to add as a child of that node. |
mesh_type | string | Yes | Primitive mesh type |
properties | object | — | Mesh properties (size, material_path, etc.) |
Parameters from the server's own tool schema.
Why add_mesh_instance is rated Medium
This tool creates a new MeshInstance3D node, which modifies the game scene structure reversibly. It is a Write operation (creates data), not Read (no retrieval), Execute (no arbitrary code/commands), Destructive (reversible via undo), or Financial. Medium severity reflects that while scene modification can affect game functionality, it's limited to adding a visual mesh object and can be undone in the editor.
From the tool's definition Tool name 'add_mesh_instance' with description 'Add a MeshInstance3D with a primitive mesh type' indicates creation of a new scene node/object in Godot.
Attacks that exploit this kind of access
The rule that runs add_mesh_instance 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_mesh_instance, this is the rule to start with:
add_mesh_instance 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_mesh_instance call is checked against it from then on.
Questions about add_mesh_instance
Add a MeshInstance3D with a primitive mesh type. 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_mesh_instance accepts 3 parameters: parent, mesh_type, properties. Required: parent, mesh_type. 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_mesh_instance: 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_mesh_instance 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_mesh_instance 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_mesh_instance. 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_mesh_instance 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