AI agents use create_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 (relative to project root, e.g. "shaders/glow.gdshader") |
type | string | Yes | Shader type template |
Parameters from the server's own tool schema.
This tool creates a new shader file (.gdshader) in a Godot project, which is a reversible Write operation. It does not execute code, delete data, or move money. The severity is medium because creating arbitrary shader files could affect game rendering or introduce malicious visual effects, but the impact is limited to the local project and can be undone by deletion.
From the tool's definition Tool name is 'create_shader' and description states 'Create a new .gdshader from template', which involves creating a new file in the game project.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Create a new .gdshader from template. 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_shader accepts 2 parameters: path, type. Required: path, 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_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_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_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_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_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_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 →