This record as markdown: /tools/keeveeg-godot-mcp/create-shader.md
What create_shader does on Godot
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 | File path for the shader (e.g. 'res://shaders/outline.gdshader') |
type | string | — | Shader type: visual/canvas_item (2D), spatial (3D), particles, sky, fog, texture_blit (default: canvas_item) |
content | string | — | Initial shader code |
Parameters from the server's own tool schema.
Why create_shader is rated Medium
This tool creates a new shader resource, which modifies the project state by adding a new file/asset. It is reversible (the shader can be deleted), so it falls under Write rather than Destructive. The severity is medium because creating arbitrary shaders could inject malicious rendering code or impact project performance, but the blast radius is limited to visual rendering unless combined with other exploits.
From the tool's definition Tool name 'create_shader' and description 'Create a new Shader resource' indicate creation of a new asset/resource file in the Godot engine project.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs create_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 create_shader, this is the rule to start with:
create_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 create_shader call is checked against it from then on.
Questions about create_shader
Create a new Shader resource. 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 3 parameters: path, type, content. Required: path. 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 (@keeveeg/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