mesh_set_surface_material
Assign a Material (res:// path) to a MeshInstance3D (undoable). Default surface -1 sets 'material_override' (whole instance); a surface index >= 0 sets that surface's override material (must be within the mesh's surface count). Refuses a non-MeshInstance3D node or a non-Material resource.
This record as markdown: /tools/breakpoint-mcp/mesh-set-surface-material.md
What mesh_set_surface_material does on Breakpoint
AI agents use mesh_set_surface_material 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 |
|---|---|---|---|
path | string | Yes | MeshInstance3D node path relative to the scene root |
surface | integer | — | Surface index, or -1 (default) for material_override |
material_path | string | Yes | Material resource res:// path (StandardMaterial3D / ShaderMaterial / …) |
Parameters from the server's own tool schema.
Why mesh_set_surface_material is rated Medium
This tool creates or modifies rendering state (material assignment) on a 3D node without permanently deleting data or executing arbitrary code. While it affects visual output, the change is reversible (undoable) and is a direct property modification rather than code execution. Write is the appropriate category as it modifies object properties in a reversible manner.
From the tool's definition Tool description states it 'Assign[s] a Material... to a MeshInstance3D (undoable)', indicating it modifies graphics rendering state by setting material overrides on mesh surfaces. The word 'undoable' confirms the action is reversible.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs mesh_set_surface_material 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 mesh_set_surface_material, this is the rule to start with:
mesh_set_surface_material 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 Breakpoint, apply this rule, and every mesh_set_surface_material call is checked against it from then on.
Questions about mesh_set_surface_material
Assign a Material (res:// path) to a MeshInstance3D (undoable). Default surface -1 sets 'material_override' (whole instance); a surface index >= 0 sets that surface's override material (must be within the mesh's surface count). Refuses a non-MeshInstance3D node or a non-Material resource. 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.
mesh_set_surface_material accepts 3 parameters: path, surface, material_path. Required: path, material_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for mesh_set_surface_material: 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.
mesh_set_surface_material 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 mesh_set_surface_material 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 mesh_set_surface_material. 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.
mesh_set_surface_material 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.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue