New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERBreakpoint SOURCEbreakpoint-mcp
Medium RISK CLASS
Category Write
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about mesh_set_surface_material

What does the mesh_set_surface_material tool do? +

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.

What parameters does mesh_set_surface_material accept? +

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.

How do I enforce a policy on mesh_set_surface_material? +

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.

What risk level is mesh_set_surface_material? +

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

Can I rate-limit mesh_set_surface_material? +

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.

How do I block mesh_set_surface_material completely? +

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.

What MCP server provides mesh_set_surface_material? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.