meshinstance_create
Add a MeshInstance3D under a parent (undoable). Optional
This record as markdown: /tools/godot-breakpoint-mcp/meshinstance-create.md
What meshinstance_create does on Godot Breakpoint
AI agents use meshinstance_create to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why meshinstance_create is rated Medium
Creating a MeshInstance3D node in Godot modifies the scene tree structure (a reversible Write operation). The '(undoable)' designation confirms this action is reversible via undo, distinguishing it from destructive operations. While it affects the editor/scene state, it does not execute arbitrary code, delete data, or trigger external operations, so it falls under Write rather than Execute or Destructive.
From the tool's definition Tool description states 'Add a MeshInstance3D under a parent (undoable)' - the 'Add' action and '(undoable)' note indicate data creation/modification that can be reversed.
Attacks that exploit this kind of access
The rule that runs meshinstance_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meshinstance_create, this is the rule to start with:
meshinstance_create 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 Breakpoint, apply this rule, and every meshinstance_create call is checked against it from then on.
Questions about meshinstance_create
Add a MeshInstance3D under a parent (undoable). Optional. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for meshinstance_create: 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 Breakpoint. Nothing to install.
meshinstance_create 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 meshinstance_create 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 meshinstance_create. 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.
meshinstance_create is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue