meshinstance_create

Add a MeshInstance3D under a parent (undoable). Optional 'mesh_path' loads a Mesh resource (e.g. a primitive_mesh_create output) and assigns it. Returns the new node's path.

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/meshinstance-create.md

WHAT IT DOES

What meshinstance_create does on Breakpoint

AI agents use meshinstance_create to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.

Parameter	Type	Required	Description
`name`	string	—	Node name (default MeshInstance3D)
`mesh_path`	string	—	Mesh resource res:// path to assign to the instance's 'mesh'
`parent_path`	string	Yes	Parent node path relative to the scene root; "." for the root

Parameters from the server's own tool schema.

RISK

Why meshinstance_create is rated Medium

This tool creates a new 3D mesh instance node, which is a reversible modification (explicitly marked 'undoable'). It does not execute arbitrary code, delete data, or move money. The creation of scene nodes in a graphics engine is a write operation. Severity is medium because misuse could clutter a scene or consume resources, but the effect is reversible and localized to the scene structure.

From the tool's definition Tool description states 'Add a MeshInstance3D under a parent (undoable)' and 'Returns the new node's path', indicating creation of a new node/resource in what appears to be a scene graph or game engine structure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meshinstance_create safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meshinstance_create": {
      "limits": [
        {
          "counter": "meshinstance_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every meshinstance_create call is checked against it from then on.

FAQ

Questions about meshinstance_create

What does the meshinstance_create tool do? +

Add a MeshInstance3D under a parent (undoable). Optional 'mesh_path' loads a Mesh resource (e.g. a primitive_mesh_create output) and assigns it. Returns the new node's path. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does meshinstance_create accept? +

meshinstance_create accepts 3 parameters: name, mesh_path, parent_path. Required: parent_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on meshinstance_create? +

Register the 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 Breakpoint. Nothing to install.

What risk level is meshinstance_create? +

meshinstance_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit meshinstance_create? +

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.

How do I block meshinstance_create completely? +

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.

What MCP server provides meshinstance_create? +

meshinstance_create is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →