This record as markdown: /tools/yanhuifair-godot-mcp/create-script.md
What create_script does on Godot
AI agents use create_script 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 |
|---|---|---|---|
path | string | Yes | Output path (relative to project root, e.g. "scripts/enemy.gd") |
type | string | Yes | Script language |
template | object | — | Template type |
class_name | object | — | Optional class_name for GDScript |
Parameters from the server's own tool schema.
Why create_script is rated Medium
Creating a script is a write operation that modifies the project state by adding new code artifacts. While reversible (scripts can be deleted), it has high severity because scripts are executable code that could introduce vulnerabilities, malicious logic, or break the application if an AI agent is tricked into creating harmful code.
From the tool's definition Tool name is 'create_script' and description states 'Create a new script from template.' This action creates a new file (a script) in the Godot project, which is a reversible write operation.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (template)
Attacks that exploit this kind of access
The rule that runs create_script 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_script, this is the rule to start with:
create_script 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_script call is checked against it from then on.
Questions about create_script
Create a new script from template. 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_script accepts 4 parameters: path, type, template, class_name. Required: path, type. 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_script: 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_script 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_script 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_script. 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_script is provided by the Godot MCP server (@yanhuifair/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