AI agents call validate_script 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 .gd file to validate (relative to project root) |
Parameters from the server's own tool schema.
This tool performs static validation/linting of GDScript code, which is a read-only operation that analyzes code for potential problems without executing it, modifying persistent state, or triggering side effects. It returns diagnostic information to the user. No data is created, destroyed, or executed as a result of this tool's operation.
From the tool's definition Tool name 'validate_script' and description 'Validate GDScript for common issues' indicate static analysis or linting functionality. The verb 'validate' combined with 'for common issues' suggests inspection without modification or execution of code.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Validate GDScript for common issues. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
validate_script 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_script: 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_script 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_script 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_script. 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_script 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_script 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 →