set_material_3d
Create and apply a StandardMaterial3D or ShaderMaterial to a mesh
This record as markdown: /tools/keeveeg-godot-mcp/set-material-3d.md
What set_material_3d does on Godot
AI agents use set_material_3d 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 |
|---|---|---|---|
path | string | Yes | MeshInstance3D node path |
properties | object | Yes | Material properties (albedo_color, metallic, roughness, shader_path, etc.) |
Parameters from the server's own tool schema.
Why set_material_3d is rated Medium
The tool creates new materials and applies them to existing meshes. This modifies the scene's visual properties but does not delete data, execute arbitrary code, move money, or trigger irreversible operations. Changes can be undone in the editor. The severity is medium rather than low because arbitrary material application across multiple meshes could degrade scene integrity or performance if misused by an agent.
From the tool's definition Tool description states 'Create and apply a StandardMaterial3D or ShaderMaterial to a mesh' — this creates and modifies material properties of 3D objects, which are reversible changes to the scene state.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_material_3d 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 set_material_3d, this is the rule to start with:
set_material_3d 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 set_material_3d call is checked against it from then on.
Questions about set_material_3d
Create and apply a StandardMaterial3D or ShaderMaterial to a mesh. 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.
set_material_3d accepts 2 parameters: path, properties. Required: path, properties. 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 set_material_3d: 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.
set_material_3d 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 set_material_3d 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 set_material_3d. 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.
set_material_3d 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