validate_export_for_platform
Validate the project for export on a specific platform with detailed checks
This record as markdown: /tools/keeveeg-godot-mcp/validate-export-for-platform.md
What validate_export_for_platform does on Godot
AI agents call validate_export_for_platform 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 for |
Parameters from the server's own tool schema.
Why validate_export_for_platform is rated Low
Validation/checking operations are read-only; they inspect the project state and report issues without modifying or executing anything. The word 'validate' and 'checks' confirm this is a read/analysis operation with no side effects.
From the tool's definition validate_export_for_platform - 'Validate the project for export on a specific platform with detailed checks'
Attacks that exploit this kind of access
The rule that runs validate_export_for_platform 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_export_for_platform, this is the rule to start with:
validate_export_for_platform 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_export_for_platform call is checked against it from then on.
Questions about validate_export_for_platform
Validate the project for export on a specific platform with detailed checks. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
validate_export_for_platform 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_export_for_platform: 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_export_for_platform 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_export_for_platform 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_export_for_platform. 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_export_for_platform 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