validate_platform_build
Validate the project for building on a specific platform, checking for issues
This record as markdown: /tools/keeveeg-godot-mcp/validate-platform-build.md
What validate_platform_build does on Godot
AI agents call validate_platform_build 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 |
|---|---|---|---|
platform | string | Yes | Platform to validate the build for |
Parameters from the server's own tool schema.
Why validate_platform_build is rated Low
The tool validates and checks the project for build issues on a specific platform. This is a read-only diagnostic operation that inspects project state without modifying or executing anything. Confidence is slightly reduced because 'validate' could theoretically trigger build processes, but the description emphasizes 'checking for issues' which strongly implies passive inspection.
From the tool's definition 'Validate the project for building on a specific platform, checking for issues' — validation and checking implies read-only inspection with no side effects
Attacks that exploit this kind of access
The rule that runs validate_platform_build 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_platform_build, this is the rule to start with:
validate_platform_build 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_platform_build call is checked against it from then on.
Questions about validate_platform_build
Validate the project for building on a specific platform, checking for issues. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
validate_platform_build accepts 1 parameter: platform. Required: platform. 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_platform_build: 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_platform_build 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_platform_build 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_platform_build. 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_platform_build 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