assign_shader_material
Create a ShaderMaterial and assign it to a node's material property
This record as markdown: /tools/keeveeg-godot-mcp/assign-shader-material.md
What assign_shader_material does on Godot
AI agents use assign_shader_material 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 |
|---|---|---|---|
node_path | string | Yes | Node path to assign the material to |
shader_path | string | Yes | Shader resource path |
Parameters from the server's own tool schema.
Why assign_shader_material is rated Medium
This tool creates a new ShaderMaterial resource and assigns it to a node, modifying the scene's material configuration. This is a reversible data modification (Write category) rather than Read (no retrieval), Execute (no arbitrary code execution), Destructive (assignable to undo), or Financial.
From the tool's definition Create a ShaderMaterial and assign it to a node's material property — uses 'Create' and 'assign' which indicate modification of node properties in the Godot editor state.
Attacks that exploit this kind of access
The rule that runs assign_shader_material 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 assign_shader_material, this is the rule to start with:
assign_shader_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 Godot, apply this rule, and every assign_shader_material call is checked against it from then on.
Questions about assign_shader_material
Create a ShaderMaterial and assign it to a node's material property. 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.
assign_shader_material accepts 2 parameters: node_path, shader_path. Required: node_path, shader_path. 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 assign_shader_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 Godot. Nothing to install.
assign_shader_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 assign_shader_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 assign_shader_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.
assign_shader_material 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