create_project_with_assets
Create a new Godot project and import specified assets into it
This record as markdown: /tools/keeveeg-godot-mcp/create-project-with-assets.md
What create_project_with_assets does on Godot
AI agents use create_project_with_assets 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 |
|---|---|---|---|
name | string | Yes | Project name |
path | string | Yes | Directory path where the project will be created |
assets | array | Yes | List of assets to import into the project |
Parameters from the server's own tool schema.
Why create_project_with_assets is rated Medium
This tool creates new project data structures and imports assets, which are reversible write operations. While it modifies the file system, it does not execute arbitrary code, run shell commands, or delete data irreversibly. The high severity reflects the broad impact of project creation and asset import on a development environment, but it remains a Write operation since these changes can be undone or reverted.
From the tool's definition Tool performs 'Create a new Godot project and import specified assets into it' — creates new project structures and modifies the file system by importing assets.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_project_with_assets 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 create_project_with_assets, this is the rule to start with:
create_project_with_assets 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 create_project_with_assets call is checked against it from then on.
Questions about create_project_with_assets
Create a new Godot project and import specified assets into it. 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.
create_project_with_assets accepts 3 parameters: name, path, assets. Required: name, path, assets. 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 create_project_with_assets: 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.
create_project_with_assets 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 create_project_with_assets 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 create_project_with_assets. 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.
create_project_with_assets 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