compile_shader
Compile (reimport) a .gdshader via Godot editor or local validation.
This record as markdown: /tools/yanhuifair-godot-mcp/compile-shader.md
What compile_shader does on Godot
AI agents invoke compile_shader to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to .gdshader file to compile (relative to project root) |
Parameters from the server's own tool schema.
Why compile_shader is rated High
This tool executes a compilation operation on shader code, which is an active operation triggering Godot's shader compilation pipeline. While shader compilation itself is generally safe and doesn't permanently modify data (compilation can be reversed by recompiling), it runs code processing that depends on the shader file argument and could trigger side effects in the running Godot editor.
From the tool's definition compile_shader: Compile (reimport) a .gdshader via Godot editor or local validation. The tool actively triggers compilation, which executes shader code processing and may reload resources in the Godot engine.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs compile_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 compile_shader, this is the rule to start with:
compile_shader stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 compile_shader call is checked against it from then on.
Questions about compile_shader
Compile (reimport) a .gdshader via Godot editor or local validation. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
compile_shader accepts 1 parameter: path. 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 compile_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.
compile_shader is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the compile_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 compile_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.
compile_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.
Across the catalogue