scaffold_project_structure
Create a standard folder structure for a Godot project
This record as markdown: /tools/keeveeg-godot-mcp/scaffold-project-structure.md
What scaffold_project_structure does on Godot
AI agents use scaffold_project_structure to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
structure | string | — | Folder structure preset |
project_path | string | Yes | Path to the Godot project root |
Parameters from the server's own tool schema.
Why scaffold_project_structure is rated Medium
This tool creates directories and potentially configuration files to establish a project structure. This is a Write operation because it creates new filesystem artifacts (folders/files) reversibly—the created structure can be deleted or reorganized. It does not execute arbitrary code, delete existing data irreversibly, or move money.
From the tool's definition Tool name 'scaffold_project_structure' and description 'Create a standard folder structure for a Godot project' indicate file/folder creation operations.
Attacks that exploit this kind of access
The rule that runs scaffold_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 scaffold_project_structure, this is the rule to start with:
scaffold_project_structure stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 scaffold_project_structure call is checked against it from then on.
Questions about scaffold_project_structure
Create a standard folder structure for a Godot project. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
scaffold_project_structure accepts 2 parameters: structure, 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 scaffold_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.
scaffold_project_structure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scaffold_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 scaffold_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.
scaffold_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