This record as markdown: /tools/keeveeg-godot-mcp/create-project-license.md
What create_project_license does on Godot
AI agents use create_project_license 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 |
|---|---|---|---|
license | string | Yes | License type |
custom_text | string | — | Custom license text (required when license is 'custom') |
project_path | string | Yes | Path to the Godot project root |
Parameters from the server's own tool schema.
Why create_project_license is rated Medium
This tool creates a new LICENSE file, which is a reversible write operation. It does not delete data, execute arbitrary code, or have financial implications. The severity is low because overwriting a LICENSE file has minimal blast radius—it affects only project metadata and can be easily corrected.
From the tool's definition Tool name 'create_project_license' and description 'Create a LICENSE file for the project' indicate file creation.
Attacks that exploit this kind of access
The rule that runs create_project_license 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_license, this is the rule to start with:
create_project_license 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_license call is checked against it from then on.
Questions about create_project_license
Create a LICENSE file for the 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.
create_project_license accepts 3 parameters: license, custom_text, project_path. Required: license, 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 create_project_license: 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_license 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_license 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_license. 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_license 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