set_shader_node_param
Set a parameter on a VisualShader node (constant, expression, operator, etc.).
This record as markdown: /tools/yanhuifair-godot-mcp/set-shader-node-param.md
What set_shader_node_param does on Godot
AI agents use set_shader_node_param 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 | Path to VisualShader .tres |
param | string | Yes | Parameter name (e.g. "constant", "expression", "operator") |
value | string | Yes | New value as a raw Godot literal (e.g. "2", "Color(1, 0, 0, 1)", "\"uv\"") |
node_index | number | Yes | Node index |
shader_stage | object | — | Shader stage (default: main stage for the shader mode) |
Parameters from the server's own tool schema.
Why set_shader_node_param is rated Medium
Modifies shader parameters reversibly, affecting visual rendering logic but not destructively or with financial impact.
From the tool's definition Set a parameter on a VisualShader node; modifies shader properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_shader_node_param 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_shader_node_param, this is the rule to start with:
set_shader_node_param 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_shader_node_param call is checked against it from then on.
Questions about set_shader_node_param
Set a parameter on a VisualShader node (constant, expression, operator, etc.). 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_shader_node_param accepts 5 parameters: path, param, value, node_index, shader_stage. Required: path, param, value, node_index. 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_shader_node_param: 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_shader_node_param 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_shader_node_param 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_shader_node_param. 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_shader_node_param is provided by the Godot MCP server (@yanhuifair/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