add_shader_graph_node
Add a node to a VisualShader graph. 40+ node types available (constants, math, textures, effects).
This record as markdown: /tools/yanhuifair-godot-mcp/add-shader-graph-node.md
What add_shader_graph_node does on Godot
AI agents use add_shader_graph_node 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 file |
params | object | — | Override default params. Values are raw Godot literals, so strings need embedded quotes: {"input_name": "\"uv\""} |
position | object | — | [x, y] position on graph canvas (default: auto-place) |
node_type | string | Yes | Node type shorthand (e.g. "color_constant", "multiply", "texture", "fresnel"). Use list_shader_node_types to see all options. |
shader_stage | object | — | Shader stage: vertex/fragment/light (Spatial, CanvasItem), start/process/collide (Particles), sky, fog. Defaults to the main stage for the shader mode. |
Parameters from the server's own tool schema.
Why add_shader_graph_node is rated Medium
Creates new shader graph nodes, modifying VisualShader resources reversibly within the Godot project.
From the tool's definition Add a node to a VisualShader graph
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs add_shader_graph_node 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 add_shader_graph_node, this is the rule to start with:
add_shader_graph_node 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 add_shader_graph_node call is checked against it from then on.
Questions about add_shader_graph_node
Add a node to a VisualShader graph. 40+ node types available (constants, math, textures, effects). 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.
add_shader_graph_node accepts 5 parameters: path, params, position, node_type, shader_stage. Required: path, node_type. 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 add_shader_graph_node: 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.
add_shader_graph_node 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 add_shader_graph_node 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 add_shader_graph_node. 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.
add_shader_graph_node 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