This record as markdown: /tools/yanhuifair-godot-mcp/write-script.md
What write_script does on Godot
AI agents use write_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 | Path to script file (relative to project root) |
content | string | Yes | New file content |
create_backup | object | — | Create .bak backup (default: true) |
Parameters from the server's own tool schema.
Why write_script is rated Medium
This tool creates or modifies script files in a Godot project. While reversible (files can be edited or deleted), writing to script files can inject code that alters game behavior, affects other systems, or introduces bugs. In a Godot engine context where scripts control game logic, this is high-severity Write rather than Execute, because the tool itself does not run the scripts—it only modifies them.
From the tool's definition Tool name is 'write_script' and description states 'Write content to a script file.' The verb 'write' and explicit mention of writing to a script file indicate data modification.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs write_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 write_script, this is the rule to start with:
write_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 write_script call is checked against it from then on.
Questions about write_script
Write content to a script file. 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.
write_script accepts 3 parameters: path, content, create_backup. Required: path, content. 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 write_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.
write_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 write_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 write_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.
write_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