Validate GDScript files and get compilation errors
AI agents call get_script_errors to retrieve information from Godot MCP Unified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation and error reporting on existing GDScript files—a read-only operation that queries the state of code without side effects. It does not execute the scripts, modify them, delete them, or trigger external operations. The output is purely informational (error messages), making this a Read category tool with low risk.
From the tool's definition The tool is described as 'Validate GDScript files and get compilation errors', which retrieves and reports information about script compilation status without modifying any data or executing code.
Attacks that exploit this kind of access
Validate GDScript files and get compilation errors. It is categorised as a Read tool in the Godot MCP Unified MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for get_script_errors: 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 MCP Unified. Nothing to install.
get_script_errors 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 get_script_errors 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 get_script_errors. 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.
get_script_errors is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →