edit_script
Edit an existing GDScript file by replacing a text segment
This record as markdown: /tools/keeveeg-godot-mcp/edit-script.md
What edit_script does on Godot
AI agents use edit_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 | Script file path (e.g. 'res://scripts/player.gd') |
new_text | string | Yes | Replacement text |
old_text | string | Yes | Exact text to find and replace |
Parameters from the server's own tool schema.
Why edit_script is rated Medium
This tool modifies an existing source code file by replacing content within it. It is a write operation (file modification), but since it replaces rather than deletes the file entirely, it is reversible in principle (e.g., via version control). However, the blast radius is high because modifying GDScript files can alter game logic, introduce bugs, or create security vulnerabilities in the Godot project.
From the tool's definition Edit an existing GDScript file by replacing a text segment
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs edit_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 edit_script, this is the rule to start with:
edit_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 edit_script call is checked against it from then on.
Questions about edit_script
Edit an existing GDScript file by replacing a text segment. 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.
edit_script accepts 3 parameters: path, new_text, old_text. Required: path, new_text, old_text. 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 edit_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.
edit_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 edit_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 edit_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.
edit_script 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