validate_project_structure
Validate a Godot project's folder structure and configuration for correctness
This record as markdown: /tools/keeveeg-godot-mcp/validate-project-structure.md
What validate_project_structure does on Godot
AI agents call validate_project_structure 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 |
|---|---|---|---|
project_path | string | Yes | Path to the Godot project root |
Parameters from the server's own tool schema.
Why validate_project_structure is rated Low
This tool checks and validates the integrity of project structure and configuration files. Validation operations are inherently read-only—they query and verify data without creating, modifying, or deleting resources. The tool has no side effects and poses minimal risk if invoked by an AI agent, as it only reports findings about existing project state.
From the tool's definition Tool name 'validate_project_structure' and description 'Validate a Godot project's folder structure and configuration for correctness' indicate inspection/verification of existing state without modification.
Attacks that exploit this kind of access
The rule that runs validate_project_structure 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_project_structure, this is the rule to start with:
validate_project_structure 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_project_structure call is checked against it from then on.
Questions about validate_project_structure
Validate a Godot project's folder structure and configuration for correctness. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
validate_project_structure accepts 1 parameter: project_path. Required: project_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_project_structure: 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_project_structure 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_project_structure 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_project_structure. 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_project_structure 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