AI agents call validate_shader to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to .gdshader file to validate (relative to project root) |
Parameters from the server's own tool schema.
This tool queries and analyzes shader code for correctness but produces no side effects—it neither executes the shader, modifies files, nor changes system state. It is purely informational/diagnostic, making it a Read category tool with low severity since misuse would only provide false validation results without harming the system.
From the tool's definition Tool performs validation/syntax checking of .gdshader files without modifying, creating, deleting, executing, or moving money. The verb 'validate' and description 'syntax issues' indicate a read-only inspection operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Validate .gdshader for syntax issues (shader_type, braces, declarations). 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 (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
validate_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 →