AI agents use create_visual_shader 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 | Output path for new VisualShader .tres |
shader_type | string | Yes | Shader mode |
Parameters from the server's own tool schema.
This tool creates a new VisualShader resource file (.tres format), which is a data creation action. It modifies the project state by adding a new asset but does not execute arbitrary code, delete existing data, or move money.
From the tool's definition 'Create a new VisualShader .tres graph file' — the tool creates a new file artifact in the Godot project, a reversible write operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Create a new VisualShader .tres graph file. 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.
create_visual_shader accepts 2 parameters: path, shader_type. Required: path, shader_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 create_visual_shader: 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.
create_visual_shader 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 create_visual_shader 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 create_visual_shader. 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.
create_visual_shader 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.
create_visual_shader is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →