This record as markdown: /tools/yanhuifair-godot-mcp/write-shader.md
What write_shader does on Godot
AI agents use write_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 | Path to .gdshader file (relative to project root) |
content | string | Yes | New shader content |
create_backup | object | — | Create .bak backup (default: true) |
Parameters from the server's own tool schema.
Why write_shader is rated Medium
This tool creates or modifies shader files, which is reversible data modification. It does not delete data (would be Destructive), does not execute arbitrary operations (would be Execute), and does not move money (Financial).
From the tool's definition Tool name 'write_shader' and description 'Write content to a .gdshader' explicitly indicate creation/modification of shader files. The verb 'write' and file extension '.gdshader' (Godot shader format) confirm this creates or modifies shader code.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs write_shader 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 write_shader, this is the rule to start with:
write_shader 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 write_shader call is checked against it from then on.
Questions about write_shader
Write content to a .gdshader. 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.
write_shader accepts 3 parameters: path, content, create_backup. Required: path, content. 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 write_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.
write_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 write_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 write_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.
write_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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue