This record as markdown: /tools/keeveeg-godot-mcp/validate-shader.md
What validate_shader does on Godot
AI agents call validate_shader to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Shader file path |
Parameters from the server's own tool schema.
Why validate_shader is rated Low
Validation/compilation checking is a read-only operation that inspects a file and reports errors without modifying any data or triggering side effects.
From the tool's definition "Validate a shader file for compilation errors"
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs validate_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 validate_shader, this is the rule to start with:
validate_shader is read-only, so it stays allowed. 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 validate_shader call is checked against it from then on.
Questions about validate_shader
Validate a shader file for compilation errors. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
validate_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 validate_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.
validate_shader is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_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 validate_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.
validate_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